ctask
Manages tasks using the ctask CLI wrapper over a local SQLite database. Use when tracking work items, creating tasks, managing dependencies, adding comments, labeling, or reviewing task status. Triggers on task tracking, ticket management, work planning, backlog management.
Best use case
ctask is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Manages tasks using the ctask CLI wrapper over a local SQLite database. Use when tracking work items, creating tasks, managing dependencies, adding comments, labeling, or reviewing task status. Triggers on task tracking, ticket management, work planning, backlog management.
Teams using ctask should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ctask/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ctask Compares
| Feature / Agent | ctask | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Manages tasks using the ctask CLI wrapper over a local SQLite database. Use when tracking work items, creating tasks, managing dependencies, adding comments, labeling, or reviewing task status. Triggers on task tracking, ticket management, work planning, backlog management.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# ctask — Local Task Tracker Use the `ctask` CLI to track tasks, dependencies, comments, and labels in a local SQLite database. ## Prerequisites `ctask` must be on `$PATH`. Database auto-initializes on first use. ## CLI Reference ### Create a task ```bash ctask create "Title" [--desc "Description"] [--priority low|medium|high|critical] [--project "name"] ``` ### List tasks ```bash ctask list [--status open|in_progress|blocked|done|cancelled] [--priority <p>] [--project <name>] [--all] ``` Default: excludes cancelled tasks. Use `--all` to show everything. ### Show task details ```bash ctask show <id> ``` Returns task fields, labels, dependencies (blocked by / blocks), and comments. ### Update a task ```bash ctask update <id> [--title "New title"] [--desc "New desc"] [--status <s>] [--priority <p>] [--project "name"] ``` ### Comments ```bash ctask comment <id> <body> # Add comment ctask comments <id> # List comments ``` ### Dependencies ```bash ctask block <id> --by <blocker_id> # Task <id> is blocked by <blocker_id> ctask unblock <id> --by <blocker_id> # Remove dependency ctask deps <id> # Show what blocks/is blocked by ``` ### Labels ```bash ctask label <id> <label> # Add label ctask unlabel <id> <label> # Remove label ctask labels <id> # List labels ``` ### Other ```bash ctask delete <id> # Permanently delete task ctask search <query> # Search title and description ``` ## When to Act | User says... | Do this | |-------------|---------| | "track this" / "add a task" / "remember to..." | `ctask create` — infer title from context, ask project if ambiguous | | "what's open" / "what am I working on" | `ctask list --status open` | | "I finished X" / marks work done | `ctask update <id> --status done` + `ctask comment <id> "outcome"` | | "X depends on Y" / "can't do X until Y" | `ctask block <X> --by <Y>` | | "I'm stuck on X" | `ctask update <id> --status blocked` + `ctask comment <id> "why"` | | starts working on a task | `ctask update <id> --status in_progress` | Always `ctask list` first to avoid creating duplicates. ## Enums - **Statuses**: open, in_progress, blocked, done, cancelled - **Priorities**: low, medium, high, critical (list output sorts by priority desc, then date desc) ## Guidelines - Always quote titles with double-quotes to avoid shell issues. - Comments are engineering logs, not status updates: - Bad: "done" / "updated status" - Good: "Fixed by switching to connection pooling — was hitting PG max_connections under load" - When completing: `update --status done` + closing comment summarizing the outcome. - When blocked: `update --status blocked` + comment explaining why + `block` if another task is the blocker. - Use `--project` to scope tasks when working across multiple projects.
Related Skills
workflow-review
Reviews Claude Code sessions and proposes workflow improvements. Use when: (1) /workflow-review command, (2) "review my workflow", "how can I improve", (3) after long sessions when nudged, (4) start of session with pending review. Analyzes tool usage patterns, CLAUDE.md configuration, and compares against CC best practices. Proposes: CLAUDE.md updates, new skills, underused CC features. Saves session summaries to .claude/workflow-reviews/ for cross-session continuity.
voice-mode
Activates voice conversation mode using Pocket TTS Docker container. Use when user says "voice mode", "let's talk", "talk to me", "speak your responses", or wants Claude to respond with spoken audio. Speaks all responses through TTS and plays via speakers.
test-quality
Guides strong, effective unit test generation using proven testing techniques. Use when writing unit tests, reviewing test quality, improving existing tests, generating test cases, checking test coverage strength, or when tests exist but may be weak. Triggers on: unit test, test quality, test coverage, write tests, improve tests, review tests, test strength, mutation testing, boundary testing.
pr-review
Reviews code changes before merging. Use when reviewing PRs, checking staged changes, reviewing diffs, code review, merge readiness check, or validating changes before commit/push.
latex-presentation
Creates impressive LaTeX Beamer presentations with modern design. Generates .tex files with theme selection, font pairing, TikZ diagrams, overlays, and best practices. Use for LaTeX slides, Beamer presentations, scaffolding decks, slide design advice, or TikZ diagram generation.
git-commit
Plans and executes git commits with optional TICKET_ID prefix. Analyzes staged changes, proposes optimal commit structure (single or multiple), generates descriptive messages with technical context, and executes after user approval. Use when committing code changes, creating atomic commits, or splitting large changesets.
codex
AI peer review via OpenAI Codex CLI. Use when reviewing code changes, validating technical decisions, comparing implementation approaches, or getting a second opinion on architecture choices. Triggers on /codex, /codex-review, or auto-triggers when presenting significant alternatives to user.
codemap
Generate navigational codebase maps with architecture diagrams. Use when mapping a codebase, creating architecture docs, visualizing project structure, generating infrastructure diagrams, understanding repo layout, or onboarding to a new project.
clarice
Conducts realistic mock interviews with detailed feedback and scoring. Use for interview prep, behavioral questions, technical interviews, STAR practice, system design interviews, or interview coaching.
c7
Fetches up-to-date library documentation from Context7 and saves to /tmp/context7/. Use when needing current API docs, code examples, library references, SDK documentation, or checking latest library versions. Triggers: context7, c7, library docs, fetch docs, current documentation, api reference.
swe-cli-skills
Senior engineer CLI expertise for AI agents — workflows, safety guardrails, gotchas, and anti-patterns across cloud, IaC, containers, databases, dev tools, and platforms
PicoClaw Fleet
Orchestrate a fleet of remote PicoClaw workers over SSH for fast, ephemeral one-shot tasks.