Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
- Added skill metadata specifying required binaries and supported installation methods (apt, brew). - No functional changes to core behavior or workflow.
What This Skill Does
Workspace-local task management using Taskwarrior as the backend. All task data is stored inside the active workspace under .openclaw/taskwarrior/, keeping tasks isolated from any global Taskwarrior configuration. Supports adding, listing, modifying, completing, and annotating tasks with project, tag, due date, and priority filtering.
Stores all task data inside the workspace directory, so task lists stay with the project and don't conflict with a user's personal Taskwarrior setup.
When to use it
- Tracking repository-specific tasks without touching global Taskwarrior data
- Assigning due dates and priorities to work items in a project
- Organizing tasks by project and tag within a codebase
- Marking tasks done and adding notes via annotations
- Filtering overdue or high-priority tasks for a specific workspace
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Add a high-priority task to fix the login bug, due tomorrow, under the 'backend' project
- 1Runs `task --version` to confirm Taskwarrior is available
- 2Creates `.openclaw/taskwarrior/` directories and initializes a workspace-local taskrc if not already present
- 3Runs `task add 'Fix login bug' project:backend priority:H due:tomorrow`
- 4Verifies the result with `task <id> info` and returns the task details
New task created with ID, confirmed with project:backend, priority:H, and due date set to tomorrow
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.