kanban-worker

Guides Hermes Kanban workers through handoffs, retries, and workspace edge cases.

1|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/Araara7/hermes-skills --skill kanban-worker-araara7
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kanban-worker
Source: https://github.com/Araara7/hermes-skills/tree/main/devops/kanban-worker
Command: npx skills add https://github.com/Araara7/hermes-skills --skill kanban-worker-araara7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Dispatched Kanban workers often mishandle task handoffs, claim cards they never created, write useless block reasons, or misdiagnose retry scenarios. This Skill provides the deeper operational detail beyond the auto-injected lifecycle guidance so workers complete, block, and hand off tasks correctly. ## Core Features & Use Cases - Structured handoff patterns: Shows correct kanban_complete summary and metadata shapes for coding, research, and review tasks, including review-required flows that block with structured comments. - Workspace and tenant handling: Explains how to work in scratch, shared directory, and git worktree workspaces, plus tenant-prefixed memory isolation. - Retry diagnostics and pitfalls: Covers interpreting prior run outcomes (timed_out, crashed, spawn_failed, reclaimed), writing effective block reasons and heartbeats, and claiming only verified created cards. - Use Case: A worker retrying a crashed task inspects prior run outcomes, chunks the work to avoid the timeout, then completes with structured metadata and verified created card IDs. ## Quick Start Load the kanban-worker skill and show me how to complete my current Kanban task with proper summary metadata and verified created cards.

Frequently Asked Questions about kanban-worker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I complete a Kanban task with structured metadata?▼

Call kanban_complete with a concise summary and a metadata object containing fields like changed_files, tests_run, and decisions. Shape the metadata so downstream reviewers and aggregators can parse it without re-reading your prose.

How do I hand off a coding task that needs human review?▼

Post the structured metadata (changed files, test counts, diff path) as a kanban_comment first, then call kanban_block with a reason prefixed 'review-required: '. The reviewer unblocks the task or requests changes via comments.

Why does claiming created cards fail on kanban_complete?▼

The kernel verifies every id in created_cards exists and was created by your profile. Only pass ids captured from successful kanban_create return values; hallucinated or reused ids block the completion and are recorded on the task's event log.

What should I do when retrying a previously failed Kanban task?▼

Run kanban_show first and inspect prior runs' outcome, summary, and error fields. A timed_out outcome means chunk the work, crashed means reduce memory, and spawn_failed usually indicates a profile config issue that warrants blocking for human help.

Can I use the hermes kanban CLI inside a containerized worker?▼

No, the CLI is not installed in containerized backends like Docker or Modal. Use the kanban_* tools instead, which work across all terminal backends; the CLI exists only for human operators at a terminal.