hermes-skills/agent-workflow/acp-subagent-selection/SKILL.md
Choose the right subagent for ACP tasks — Kimi vs OpenCode vs direct execution
npx skillsauth add ariffazil/openclaw-workspace acp-subagent-selectionInstall 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.
ACP background tasks cannot handle interactive permission prompts. Select the right agent based on the task type.
| Agent | ACP Mode | Best For | Limitation | |-------|----------|----------|------------| | Kimi | ✅ Background capable | Reasoning, research, multi-step analysis | ❌ Blocked by interactive permission prompts in background mode | | OpenCode | ✅ Full file access | File operations, code refactoring, writing | ⚠️ May produce thin output in long sessions — verify results | | Direct (Hermes) | n/a | Small-medium additive changes, auditing, verification | ❌ 4300+ line mechanical refactors = slow for human |
Task type?
├── Read-only / research / reasoning
│ └── Kimi ACP (background OK if task is self-contained)
├── File write / refactor / multi-file changes
│ └── OpenCode OR direct execution
│ ├── Small (<100 lines, additive): OpenCode OK
│ └── Large (1000+ lines, mechanical): Arif direct
└── Verification / auditing
└── Hermes directly (no subagent needed)
Task: Decompose 4300-line monolith.py into 36 atomic tools + 12 prompts + 21 resources
What happened:
Lesson: Large mechanical refactors (adding @mcp.tool() decorators + async wrappers around existing logic) are additive and low-break-risk. Better done directly by Arif or chunked into <100 line pieces per OpenCode run.
After any subagent completes:
git -C ~/WEALTH diff --stat
git -C ~/WEALTH log --oneline -3
Check: expected files modified? Commit message accurate? Output matches actual changes?
development
Governed intelligence skill for AAA as the abstraction, attestation, and abduction control plane across arifOS, APEX, A-FORGE, GEOX, WEALTH, WELL, and the ariffazil profile repository. Use when the user asks to explain or design AAA, route agentic work, reduce chaos/entropy in an arifOS federation task, create AREP/task declarations, classify risk, plan multi-repo changes, review governance boundaries, or translate human intent into evidence-backed, authority-safe, recursively agentic workflows. Provides deterministic F1-F13 floor checking, bounded abduction, and FederationReceipt composition.
development
Check every skill’s “use when” and “do not use when” clauses for collisions, missing negatives, and vague verbs like “help,” “assist,” or “improve.” Load when linting, reviewing, or validating trigger boundaries.
development
Bootstrap, design, and package new skills. Load when capturing user intent for a new skill or drafting its initial instruction framework.
content-media
Diagnose which federation services are up, down, or drifting. Produce a prioritized remediation plan.