How do I install the Ctask skill?

Run npx skillmds add majiayu000/ctask in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ctask safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ctask?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ctask free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ctask by majiayu000 — Agent Skill

Name: Ctask
Rating: 4.2 (5 reviews)
Author: majiayu000

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.

majiayu000 42c5d99 2 files · 4.0 KB Updated Sep 9, 2026 567 repo stars

File contents

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

ctask create "Title" [--desc "Description"] [--priority low|medium|high|critical] [--project "name"]

List tasks

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

ctask show <id>

Returns task fields, labels, dependencies (blocked by / blocks), and comments.

Update a task

ctask update <id> [--title "New title"] [--desc "New desc"] [--status <s>] [--priority <p>] [--project "name"]

Comments

ctask comment <id> <body>       # Add comment
ctask comments <id>             # List comments

Dependencies

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

ctask label <id> <label>       # Add label
ctask unlabel <id> <label>     # Remove label
ctask labels <id>              # List labels

Other

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.

---name: ctaskdescription: 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.--- # 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.

Frequently asked questions