Content
92%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.
An exemplary orchestration skill body: a lean overview that delegates detail to a well-organized one-level-deep reference bundle, with fully concrete routing rules, exact interaction phrasings, and explicit validation and recovery checkpoints throughout the phase workflow. The only weakness is density — the completion-contract and handoff sections compress many conditions into run-on sentences that could be tightened. Suggestions: none needed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with operational rules and contains no explanations of concepts Claude already knows, but the "Mandatory Completion Contract" paragraph ("A run is complete when its output contract's done condition is met. Every normal interactive branch that produces a plan artifact or checkpoint is incomplete until...") and the Phase 5 STOP paragraph overlap and pack many nested conditions into long run-on sentences that could be trimmed. This fits 'efficient; minor instances of over-explanation that could be trimmed' rather than the fully lean 5 or the noticeably verbose 3. | 4 / 5 |
Actionability | For an instruction-only orchestration skill the guidance is fully executable: exact phrasings to use ("ask exactly: 'Plan ready at `<absolute path to plan>`. What would you like to do next?'"), exact failure tokens ("Return the exact token `settled-decision-invalidated`"), exact blocked-state fields ("`status: blocked`, `phase`, `blocker`, and `recovery_path`"), and exact per-phase reference reads. Specific decision rules cover the common routing cases (Durable-regardless-of-size conditions, tier escalation), matching 'copy-paste ready... specific examples cover the common cases'. | 5 / 5 |
Workflow Clarity | Phases 0-5 run in explicit order with checkpoints and error recovery: the resume check (Phase 0.1), source check (Phase 0.2), scoping synthesis, the Phase 5.1.5 confirmation before writing, the confidence path, and mandatory non-interactive document review. Failure handling is explicit ("If a required reference cannot be read, stop before the action it governs and report the blocker and recovery path"; "If the selection arrives after a user turn, reload `references/plan-handoff.md` before acting"), and completion criteria are precisely defined per output tier. This matches the 'clear sequence with explicit validation steps; feedback loops for error recovery' anchor. | 5 / 5 |
Progressive Disclosure | The 60-line body is a pure overview that routes each phase to a named, existing bundle file read at the moment it is needed (output-mode.md, resume.md, intake.md, research.md, structure.md, plan-sections.md, final-review.md, reasoning-elevation.md, plan-handoff.md, output-contracts.md, all verified present in references/), with the bulk of detail correctly split into references/, references/agents/, and scripts/. References are one level deep, clearly signaled with when-to-read instructions, and navigation is easy, matching the 'clear overview with well-signaled one-level-deep references' anchor. | 5 / 5 |
Total | 19 / 20 Passed |