Content
53%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.
The SKILL.md body is lean and clearly organized with a deterministic, well-sequenced routing procedure. Its critical weakness is the reference layer: the routing map and deterministic decision order it depends on are missing from the bundle, several listed references do not exist, and three actual bundle files are orphaned with no inbound links.
Suggestions
Ship the routing map and deterministic decision order inside the skill bundle (e.g., references/routing-map.json and references/deterministic-stage-routing.md) or inline the stage set and precedence table in SKILL.md, since the Procedure and Validation steps cannot execute without them.
Fix the References section: remove or restore the missing references/evals.yaml and references/task-profile.json, and correct the ../../references/* paths that resolve outside the bundle.
Link the orphaned bundle files (context-preservation.md, heartbeat-routing-preservation.md, role-resolution-fallback.md) from the body or References section so their content is discoverable, and drop the duplicated text of Procedure steps 8-9 in favor of those references.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is terse and well-sectioned with no explanations of concepts Claude already knows. Not a 5 because the Philosophy section adds little operational value and Procedure steps 8-9 ('Resolve mapped roles...', 'Return outputs with...') duplicate text preserved verbatim in references/context-preservation.md and references/role-resolution-fallback.md. | 4 / 5 |
Actionability | Procedure steps 4-7 give concrete, stage-named routing rules, which is real executable guidance. However the core lookup inputs — the stage set in '../../references/routing-map.json' and the deterministic decision order in '../../references/deterministic-stage-routing.md' — resolve to files that do not exist in the bundle, so the skill's central decision procedure cannot actually be executed. That missing key detail places it at the 'incomplete' anchor rather than 4. | 3 / 5 |
Workflow Clarity | A clear 10-step sequence exists with an explicit terminal fallback ('return blocked with exactly one missing input') and a Validation section with fail-fast gating. But the validation checkpoints ('Ensure selected stage is in the HE stage set from routing-map.json') depend on a nonexistent artifact, leaving the gates unexecutable — sequence present but checkpoints broken, matching the anchor 3 description rather than 4's 'most checkpoints present'. | 3 / 5 |
Progressive Disclosure | Scored against the actual bundle: of the files cited in the body and References section, only references/contract.yaml exists; references/evals.yaml and references/task-profile.json are missing, and all seven '../../references/*' links point outside the bundle to a nonexistent directory. Meanwhile three of the four real bundle files (context-preservation.md, heartbeat-routing-preservation.md, role-resolution-fallback.md) are never linked from SKILL.md, making them undiscoverable. The navigation layer is broken despite well-organized in-file sections, fitting the anchor 2 'references are buried/minimal structure' case better than 3. | 2 / 5 |
Total | 12 / 20 Passed |