Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Workspace-local task management powered by Taskwarrior. Add, organize, and track tasks by project, tags, due dates, and priority with all data stored inside...
Workspace-local task management powered by Taskwarrior. Add, organize, and track tasks by project, tags, due dates, and priority with all data stored inside...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
taskwarrior
Manage tasks using Taskwarrior as the backend with data stored inside the current workspace. This skill provides a safe, workspace-scoped wrapper for common Taskwarrior operations (add/list/modify/done/projects/tags/due/priority/annotations).
This skill requires Taskwarrior to already be available in the runtime environment (e.g., included in the base image). Validation: run task --version If missing: report the dependency and instruct the environment owner to install system package taskwarrior (some distros package it as task). This skill does not perform system-level installs (no apt, brew, dnf, etc.).
The skill resolves the workspace root at runtime: If set, use the first available of: OPENCLAW_WORKSPACE WORKSPACE PROJECT_DIR REPO_ROOT Otherwise, fallback to the current working directory. All Taskwarrior data is stored under: <workspace>/.openclaw/taskwarrior/
taskrc: <workspace>/.openclaw/taskwarrior/taskrc data dir: <workspace>/.openclaw/taskwarrior/.task/ Every Taskwarrior command MUST run with: TASKRC=<workspace>/.openclaw/taskwarrior/taskrc (optional) TASKDATA=<workspace>/.openclaw/taskwarrior/.task Never write to global ~/.task or ~/.taskrc unless the user explicitly asks to use global storage.
Check dependency Run: task --version If missing: stop and return dependency instructions (see references/clawhub_notes.md). Initialize workspace storage Ensure directories exist: <workspace>/.openclaw/taskwarrior/ <workspace>/.openclaw/taskwarrior/.task/ Ensure <workspace>/.openclaw/taskwarrior/taskrc contains at least: data.location=<workspace>/.openclaw/taskwarrior/.task confirmation=off verbose=off Execute requested operations Prefer stable/common commands (see references/taskwarrior_cheatsheet.md). Verify results After any mutation, show a focused task <id> info or filtered task <filter> list.
Add tasks: task add ... List tasks: task list, task <filter> list Modify tasks: task <id> modify ... Complete tasks: task <id> done Start/stop: task <id> start|stop (if desired) Projects/tags: task projects, task tags, project:<name>, +tag, -tag Due/priorities: due:<date>, priority:H|M|L Notes: task <id> annotate "..."
Follow references/safe_command_policy.md. Highlights: No delete/purge unless explicitly requested. Avoid broad bulk changes without previewing the matching set. No global config writes by default.
references/workspace_data_layout.md references/taskwarrior_cheatsheet.md references/safe_command_policy.md references/examples.md references/clawhub_notes.md
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.