Menu
Manage tasks with the `task` (Taskwarrior) CLI. Use when the user asks to review tasks, get task summaries, add work items, or complete tasks.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use tmux instead of background bash for long-running, interactive, inspectable, or user-attachable terminal processes. Use for development servers, watch-mode tests, REPLs, debuggers, interactive CLIs, log tailing, and commands that may run indefinitely or need later input/inspection.
Use Jujutsu (`jj`) for version control operations including status, history, diffs, commits, rebases, splits, squashes, and Git interop. Use when a repository is initialized for jj or the user asks for jj/Jujutsu workflows.
Create and maintain AGENTS.md files that provide AI coding agents with project context, commands, code style, and boundaries. Use when updating an existing AGENTS.md, creating a new AGENTS.md for a repository, or improving agent instructions for a codebase.
Convert public ChatGPT share links into clean Markdown transcripts for agent context. Use when a user provides a https://chatgpt.com/share/... URL and wants the conversation summarized, archived, or reused as input context.
Search the web with DuckDuckGo using the `ddgr` CLI. Use when the user asks to look something up online, verify facts, or gather source links.
Use the GitHub CLI (`gh`) for repository operations including PR and issue inspection, GitHub search, checks, and API calls. Use when a user asks for GitHub URLs, PR metadata, issue details, checks, or repository automation.
| name | taskwarrior |
| description | Manage tasks with the `task` (Taskwarrior) CLI. Use when the user asks to review tasks, get task summaries, add work items, or complete tasks. |
Inspect and manage tasks with task.
task +PENDING export
Preferred command (JSON output):
task +PENDING export
With custom filters:
task project:work due:today +PENDING export
For tasks that fall between two dates (entry, completion, due, or modified time), use Bash variables:
start_date="<start-date>"
end_date="<end-date>"
task "((entry.after:${start_date} and entry.before:${end_date}) or (end.after:${start_date} and end.before:${end_date}) or (due.after:${start_date} and due.before:${end_date}) or (modified.after:${start_date} and modified.before:${end_date}))" export
Use task rc.verbose=nothing ... for concise text output when not using export.
Build summary counts with these commands:
task +PENDING export
task +OVERDUE export
task due:today +PENDING export
task due:tomorrow +PENDING export
task priority:H +PENDING export
Summarize counts plus notable tasks (for example overdue or high priority).
Get one task by ID or UUID:
task <task-id-or-uuid> export
Create a task (mutating):
task add "Write Q1 planning notes" project:planning due:tomorrow priority:M +work +writing
Mark task done (mutating):
task <task-id-or-uuid> done
task ... export and task ... listing/info commandstask add, task <id> done, task modify, task delete