Skill

task

From sundial-org-awesome-openclaw-skills-4

Dispatches task management to Tasker docstore CLI tool: lists due today/overdue/weekly tasks, adds/moves/completes tasks. Use for natural language queries or /task commands.

cli-tools

developer-tools

Install

npx claudepluginhub joshuarweaver/cascade-ai-ml-agents-misc-2 --plugin sundial-org-awesome-openclaw-skills-4

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Route task-related requests to `tasker_cmd` (raw args only, no leading `tasker`).

Supporting Assets

README.md

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.2k

mcp-builder

9 files

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

anthropics-skills-13

124.2k

canvas-design

20 files

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

anthropics-skills-13

124.2k

Stats

Stars586

Forks75

Last CommitFeb 1, 2026

Actions

View Source View Plugin View on GitHub View README

Tags

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-ndjson unless explicitly requested.
For chat-friendly output (Telegram/WhatsApp), add --format telegram. Use --all only 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 search includes 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 today" -> add "<task>" --today [--project <name>] --format telegram
"add |
" -> add --text "<task> | <details>" --format telegram
"capture " -> capture "<text>" --format telegram
"mark done" -> done "<title>"
"show config" -> config show