Content
75%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, actionable routing skill with a clear workflow and an explicit validation checkpoint. The main improvement areas are trimming repeated 'do not run inline' restatements and converting the per-host invocation guidance into literal code blocks.
Suggestions
Consolidate the 'do not run the child CLI inline from this parent session' rule into one authoritative location (e.g. the Output contract) and reference it, rather than restating it across ~5 sections.
Render the per-host subagent invocations as literal copy-pasteable code blocks (e.g. a full Agent/Task tool call example) instead of prose descriptions, to push actionability toward 5.
If the Codex/Cursor installation-detection and limitation notes grow, move them into a references/ file to keep the overview lean and support progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Dense and assumes Claude's competence (no preamble about what an IDE/CLI is); the 'do not run the child CLI inline' rule is restated across ~5 sections, which is mild over-emphasis that could be trimmed, keeping it just below a 5. | 4 / 5 |
Actionability | Gives concrete per-host invocation syntax (subagent_type=worker, @worker, spawn_agent with fork_turns="none" + wait_agent), a detection command (`ls "${CODEX_HOME:-$HOME/.codex}/agents/"`), and a worker block template; not a 5 because the invocations are prose-described rather than literal copy-paste code blocks. | 4 / 5 |
Workflow Clarity | A clear 3-step sequence (parse intent → invoke worker → relay reply) with a validation checkpoint (the agents-dir ls check) and explicit error routing ('empty listing means the role is not installed — say so'); not a 5 because the validation is a single light check rather than a full validate-fix-retry loop. | 4 / 5 |
Progressive Disclosure | Self-contained with clear section headers (When to use, Workflow, Output contract, Scope boundaries) and no bundle files; at ~100 lines it exceeds the 50-line simple-skill threshold, so it sits at 4 rather than 5 despite good organization. | 4 / 5 |
Total | 16 / 20 Passed |