7.4k★by amirbrooks
task – OpenClaw Skill
task is an OpenClaw Skills integration for planning workflows. Tasker docstore task management via tool-dispatch. Use for task lists, due today/overdue, week planning, add/move/complete, or explicit /task commands.
Skill Snapshot
| name | task |
| description | Tasker docstore task management via tool-dispatch. Use for task lists, due today/overdue, week planning, add/move/complete, or explicit /task commands. OpenClaw Skills integration. |
| owner | amirbrooks |
| repository | amirbrooks/task |
| language | Markdown |
| license | MIT |
| topics | |
| security | L1 |
| install | openclaw add @amirbrooks/task |
| last updated | Feb 7, 2026 |
Maintainer

name: task description: Tasker docstore task management via tool-dispatch. Use for task lists, due today/overdue, week planning, add/move/complete, or explicit /task commands. user-invocable: true disable-model-invocation: false command-dispatch: tool command-tool: tasker_cmd command-arg-mode: raw metadata: {"clawdbot":{"emoji":"🗂️"}}
Route task-related requests to tasker_cmd (raw args only, no leading tasker).
- For natural language, translate the request into CLI args.
- For
/task ..., pass the args through unchanged. - Prefer human-readable output. Avoid
--stdout-json/--stdout-ndjsonunless explicitly requested. - For chat-friendly output (Telegram/WhatsApp), add
--format telegram. Use--allonly when done/archived are explicitly requested. - This is the natural-language profile. For slash-only, use
skills/task-slash/. - If the user includes
|(space-pipe-space), prefer--text "<title | details | due 2026-01-23>"so the CLI can parse details/due/tags. Only split on explicit|to avoid corrupting titles. - Do not guess separators like "but" or "—"; only split on explicit
|. - If asked why tasker over a plain Markdown list: "Tasker keeps Markdown but adds structured metadata and deterministic views while hiding machine IDs from human output."
- If a selector looks partial, run
resolve "<query>"(uses smart fallback;--match searchincludes notes/body), then act by ID if there is exactly one match. Never show IDs in human output. - For notes, prefer
note add <selector...> -- <text...>to avoid ambiguity; without--, tasker will attempt to infer the split.
Common mappings:
- "tasks today" / "overdue" ->
tasks --open --format telegram(today + overdue) - "what's our week" ->
week --days 7 --format telegram - "show tasks for Work" ->
tasks --project Work --format telegram - "show board" ->
board --project <name> --format telegram - "add <task> today" ->
add "<task>" --today [--project <name>] --format telegram - "add <task> | <details>" ->
add --text "<task> | <details>" --format telegram - "capture <text>" ->
capture "<text>" --format telegram - "mark <title> done" ->
done "<title>" - "show config" ->
config show
/task skill (tasker docstore)
Profiles:
- Natural language (this folder): NL +
/taskwithdisable-model-invocation: false - Slash-only: copy
skills/task-slash/into your skills folder astask/(low-bloat)
This skill uses:
command-dispatch: toolfor deterministic behavior
It expects:
- plugin tool
tasker_cmdallowlisted (recommended) taskerCLI available via pluginbinaryconfig,TASKER_BIN, or PATH
See docs/CLAWDBOT_INTEGRATION.md at repo root for end-to-end setup.
Permissions & Security
Security level L1: Low-risk skills with minimal permissions. Review inputs and outputs before running in production.
Requirements
- OpenClaw CLI installed and configured.
- Language: Markdown
- License: MIT
- Topics:
FAQ
How do I install task?
Run openclaw add @amirbrooks/task in your terminal. This installs task into your OpenClaw Skills catalog.
Does this skill run locally or in the cloud?
OpenClaw Skills execute locally by default. Review the SKILL.md and permissions before running any skill.
Where can I verify the source code?
The source repository is available at https://github.com/openclaw/skills/tree/main/skills/amirbrooks/task. Review commits and README documentation before installing.
