Content
50%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-sectioned, safety-conscious routing skill that clearly delineates scope, handoff targets, and output structure. It loses points for repeated reference pointers, broken external reference paths, and a procedure that stays high-level rather than giving concrete executable mechanics.
Suggestions
Collapse the repeated "See references/hot-path-folded-context.md for folded X detail" pointers into a single consolidated pointer to avoid near-duplicate lines across sections.
Resolve or remove the ../../references/*.md links that do not exist in the bundle so navigation is not broken.
Tighten the Procedure into explicit, complete steps with a concrete validation feedback loop (reconstruct -> validate gates -> route or blocked_reason) instead of a trailing step 4.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean and assumes Claude's competence (no basic-concept padding), but the "See references/hot-path-folded-context.md for folded ... detail" line is repeated ~6 times and the context-disposition policy sentence is duplicated verbatim (Gotchas and References), which is noticeable padding that could be tightened. | 3 / 5 |
Actionability | Guidance is concrete in places (enumerated output fields, an explicit handoff routing table, pass/fail/blocked gates), but the core procedure stays abstract ("Reconstruct lifecycle state from ... evidence", "Resolve only enough context") with no executable mechanics or specific read paths, leaving key details implicit. | 3 / 5 |
Workflow Clarity | A numbered procedure and dedicated Validation/Failure Handling sections provide checkpoints (pass/fail/blocked, blocked_reason), but the procedure is only four steps with step 4 trailing off into a reference bullet, and the validation feedback loop (fail -> fix -> retry) is implied rather than explicitly sequenced. | 3 / 5 |
Progressive Disclosure | SKILL.md acts as an overview pointing to one-level-deep bundle files (contract.yaml, evals.yaml, hot-path-folded-context.md), but several referenced ../../references/*.md paths do not resolve in the bundle and the hot-path file is redundantly pointed to from nearly every section, weakening navigation. | 3 / 5 |
Total | 12 / 20 Passed |