Content
88%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 three-phase workflow with concrete blocked conditions, exact template and tool-call names, and well-signaled references to real bundle files. The only deductions are minor — slight repetition of the read-only rules and a second-hop reference (review-contract.md) that is not linked directly from the overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and directive with no concept explanations — "Determine whether the implementation solves the stated problem. Be adversarial about evidence." — and it assumes competence throughout. Not 5 because the read-only rule is restated ("Remain read-only. Never edit code, tests, plans, or state." followed shortly by "Never edit or write.") and the output-format rules duplicate reviewer-prompt.md's Output section, so a few tokens could be trimmed. | 4 / 5 |
Actionability | For an instruction-only skill the guidance is fully executable: exact decision rules ("If the model matches the work model, return `blocked`", "If the packet or diff file is missing and cannot be read, return `blocked` and name the missing input"), an exact artifact name ("the `factory.review.v5` template"), and exact tool-call semantics for `subagent_done` and `caller_ping` including the shutdown-reply stop condition. A subagent can follow this without guessing. | 5 / 5 |
Workflow Clarity | A clear three-phase sequence (Isolate the session → Review the task → Return the verdict) with explicit validation checkpoints and error-recovery paths: the blocked conditions are checked before review begins and require naming the missing input, and "If it replies that the session is shutting down, stop. Do not call it again" handles the terminal failure case. The operation is read-only, so the destructive/batch validation cap does not apply. | 5 / 5 |
Progressive Disclosure | All three referenced files exist and are well-signaled one level deep with purpose statements ("Read [references/reviewer-prompt.md] and follow it", "apply [references/code-quality.md]", "the `factory.review.v5` template in [references/output.md]"). Not 5 because review-contract.md is only reachable via a second hop through reviewer-prompt.md and is never linked from SKILL.md, and the output rules are duplicated between SKILL.md and reviewer-prompt.md rather than split cleanly. | 4 / 5 |
Total | 18 / 20 Passed |