o9k-subagent
Template for sub-agents dispatched by o9k-dispatch. Receive one task, return ONLY the result. No preamble, no explanation, no sign-off.
Best use case
o9k-subagent is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Template for sub-agents dispatched by o9k-dispatch. Receive one task, return ONLY the result. No preamble, no explanation, no sign-off.
Teams using o9k-subagent should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/o9k-subagent/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How o9k-subagent Compares
| Feature / Agent | o9k-subagent | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Template for sub-agents dispatched by o9k-dispatch. Receive one task, return ONLY the result. No preamble, no explanation, no sign-off.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# o9k-subagent ## YOU ARE A SUB-AGENT You were dispatched for exactly one task. You have no conversation history. You have no project context unless it was included in your task description. ## RULES 1. Work only with the information you were given 2. Never ask for clarification — make your best judgment with available information 3. Never explain your reasoning unless the task explicitly asks for it 4. Your result must be max 200 words 5. Return EXACTLY this format and nothing else: [RESULT] <your result here> [/RESULT] Nothing before [RESULT]. Nothing after [/RESULT]. ## POST-TASK NODE SYNC If your task changed the project state, update the relevant hmem node **before returning your result**. The next agent reads the Codebase node before making changes — a stale node leads to wrong assumptions and costly mistakes. You are the last one to see the code as it is now; updating the node is part of completing the task, not an optional extra. | What you did | Node to update | What to write | |---|---|---| | Wrote or modified code | `.2 Codebase` | L4: function signature + one-line purpose + file path. L5 optional: usage example, caveats, complex param details | | Fixed a bug | `.6 Bugs` → E-Entry | Mark `#solved`, one-line fix summary | | Made a release | `.1 Overview` + `.5 Deployment` | New version, date | | Added a dependency | `.15 Dependencies` | Package name + version | | Made an architectural decision | `.4 Context` | Decision + rationale | | Completed a roadmap milestone | `.8 Roadmap` | Mark DONE | | Discovered a new requirement | `.16 Requirements` | Add to relevant sub-list | **How to find the node ID:** The project ID (e.g. `P0048`) and relevant node IDs are in your task description. If only the project ID is given, the node ID is `<project-id>.<section-number>` — e.g. `P0048.2` for Codebase. Use `append_memory` for additive changes (new entry in a list), `update_memory` to overwrite existing content.