{"skill":{"slug":"task","displayName":"Task","summary":"Tasker docstore task management via tool-dispatch. Use for task lists, due today/overdue, week planning, add/move/complete, or explicit /task commands.","description":"---\nname: task\ndescription: Tasker docstore task management via tool-dispatch. Use for task lists, due today/overdue, week planning, add/move/complete, or explicit /task commands.\nuser-invocable: true\ndisable-model-invocation: false\ncommand-dispatch: tool\ncommand-tool: tasker_cmd\ncommand-arg-mode: raw\nmetadata: {\"clawdbot\":{\"emoji\":\"🗂️\"}}\n---\n\nRoute task-related requests to `tasker_cmd` (raw args only, no leading `tasker`).\n\n- For natural language, translate the request into CLI args.\n- For `/task ...`, pass the args through unchanged.\n- Prefer human-readable output. Avoid `--stdout-json`/`--stdout-ndjson` unless explicitly requested.\n- For chat-friendly output (Telegram/WhatsApp), add `--format telegram`. Use `--all` only when done/archived are explicitly requested.\n- This is the natural-language profile. For slash-only, use `skills/task-slash/`.\n- 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.\n- Do not guess separators like \"but\" or \"—\"; only split on explicit ` | `.\n- 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.\"\n- If a selector looks partial, run `resolve \"<query>\"` (uses smart fallback; `--match search` includes notes/body), then act by ID if there is exactly one match. Never show IDs in human output.\n- For notes, prefer `note add <selector...> -- <text...>` to avoid ambiguity; without `--`, tasker will attempt to infer the split.\n\nCommon mappings:\n- \"tasks today\" / \"overdue\" -> `tasks --open --format telegram` (today + overdue)\n- \"what's our week\" -> `week --days 7 --format telegram`\n- \"show tasks for Work\" -> `tasks --project Work --format telegram`\n- \"show board\" -> `board --project <name> --format telegram`\n- \"add <task> today\" -> `add \"<task>\" --today [--project <name>] --format telegram`\n- \"add <task> | <details>\" -> `add --text \"<task> | <details>\" --format telegram`\n- \"capture <text>\" -> `capture \"<text>\" --format telegram`\n- \"mark <title> done\" -> `done \"<title>\"`\n- \"show config\" -> `config show`\n","tags":{"latest":"0.1.0"},"stats":{"comments":0,"downloads":6813,"installsAllTime":44,"installsCurrent":44,"stars":0,"versions":1},"createdAt":1769123617767,"updatedAt":1778986988254},"latestVersion":{"version":"0.1.0","createdAt":1769123617767,"changelog":"Initial release of the task skill for natural-language task management.\n\n- Handles task management requests by dispatching commands to Tasker via tool-dispatch.\n- Supports natural language to CLI arg translation; passes through explicit /task commands.\n- Produces human-friendly, chat-optimized outputs by default (Telegram/WhatsApp compatible).\n- Implements logic for parsing multi-part task titles/details/dates when explicit separators are used.\n- Supports intuitive mappings for today’s tasks, week planning, adding/completing tasks, and project/task board views.\n- Falls back to selector resolution when task references are ambiguous, always hiding machine IDs from output.","license":null},"metadata":{"setup":[],"os":null,"systems":null},"owner":{"handle":"amirbrooks","userId":"s179hm17bbjfv40c8cjfxq47wn885yvy","displayName":"amirbrooks","image":"https://avatars.githubusercontent.com/u/224349976?v=4"},"moderation":null}