Tasks

Skill anubhavmohandas/Hermes/skills/tasks

HERMES task decomposition sub-skill. Apollo routes here for task/plan/break-down/todo/track requests. Uses the TaskCreate/TaskUpdate pattern to decompose and track work, and logs completions into Mnemos v1. Extension point for deeper Task-Master-style slash commands is noted but not built in Phase 3A.From its SKILL.md

Install

npx -y skills add anubhavmohandas/Hermes --skill tasks

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.6 KB, as published. Nobody here has run it

skills/tasks — Task decomposition sub-skill

Called by Apollo, not directly by the user.

What this does in Phase 3A

Accept a task description from Apollo.
Decompose it into concrete subtasks using TaskCreate (one call per subtask, or a batch if the tool supports it) — same pattern used everywhere else in this HERMES build itself.
Track progress with TaskUpdate as work proceeds (pending → in_progress → completed).
On completion, write a short outcome line into Mnemos v1: python3 mnemos/store.py write "<session_id>" "assistant" "completed: <task>"
Return the task list with current status to Apollo.

Ground rule

Don't create a task list for something that's genuinely one step — that's noise, not tracking. Match the granularity to what actually has multiple distinct pieces of work.

What this explicitly does NOT do yet

No Task Master-style custom slash commands (/task:decompose, etc.) — not scheduled to a specific phase in the current blueprint; revisit if the plain TaskCreate/TaskUpdate pattern turns out to be insufficient.
No cross-session task persistence beyond what Mnemos v1 already logs as plain text — a real durable task store is Cron/Delegation territory, Phase 3C.