skills/o9k-dispatch/SKILL.md
Dispatch an isolated sub-agent that returns only [RESULT]...[/RESULT]. Use for any search, lookup, 'does X exist?', 'find Y', calculation, or isolated writing — never do these inline when dispatch fits.
npx skillsauth add Bumblebiber/hmem o9k-dispatchInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Always dispatch for:
.2 Codebase) in the task so the sub-agent can sync them after completing the work. Always include in the task: "Invoke superpowers:coding-discipline before writing code."Never dispatch for tasks that require knowing the conversation context.
The key rule for searching: if you're about to run grep, find, read, or search_memory to answer a question — dispatch instead. The sub-agent explores, you synthesize the result.
Write out before dispatching:
npx tsc --noEmit, grep "pattern" file.ts). Use for tasks that produce code or file changes.Send the sub-agent ONLY this prompt — no conversation history, no project context unless the task explicitly requires it:
Take ONLY the content between [RESULT] and [/RESULT]. If [VERIFY_RESULT] is present: check pass/fail. On fail, report the verification error instead of declaring the task complete. Discard all sub-agent reasoning and preamble. Use the result directly in the main conversation.
tools
Update flow for its-over-9k (hmem). Runs `npm update -g`, syncs skills, applies migrations, verifies hooks, shows the changelog. Use when the user asks to update/upgrade hmem, o9k, o9k-mcp, or its-over-9k (any language), or when the startup version-check flags a new release. Runs the npm update itself — don't assume it's already done.
development
Mandatory entry point for every Cortex session — invoke at conversation start, after /clear, and after any load_project call. All stable context (H-entries, projects, device, sync) is pre-injected by the hook — no read_memory(mode='essentials') needed. Surfaces pending git work, Next Steps + open T-tasks, and runs the O-entry routing check.
tools
Curate an .hmem file (your own or foreign) — mark obsolete/irrelevant, fix titles, consolidate duplicates, repair broken links. **Requires the `hmem-curate` MCP server** (skill prompts the user to enable it on entry). Use whenever the user says 'aufräumen', 'memory aufräumen', 'Speicher aufräumen', 'hmem aufräumen', 'clean up memory', 'tidy up hmem', 'curate memory', 'consolidate duplicates', 'merge duplicate entries', 'fix broken links', 'kümmer dich um die Memory', or invokes /o9k-curate. Also trigger when `memory_health()` flags BLOCKER/WARNING issues, when a P-entry's load_project output exceeds 4k tokens (session-start noise check defers to this skill), or before any batch cleanup of L, E, D, P entries. Skipping this skill and editing memory directly bypasses health checks, severity triage, and obsolete-chain integrity — never curate without it.
testing
Add a new rule and place it correctly — decide between a cross-project R-entry and a project-specific subnode under the active project's Rules section. Use whenever the user says 'neue Regel', 'Regel hinzufügen', 'new rule', 'add a rule', or invokes /o9k-new-rule. Critical safeguard: project-specific rules placed as R-entries pollute the session-start Rules listing across every project — get the scope right BEFORE writing.