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.
A tightly compressed, well-structured process skill: lean prose, a fully sequenced procedure with explicit validation gates and rerun loops, and condition-based routing to reference files. The main gaps are the absence of any concrete example artifact or command invocation and heavy reliance on out-of-bundle shared references.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense, unpadded directive prose: every section states policy or instructions with no explanation of concepts Claude already knows and no filler (e.g., 'Strategy artifacts are cognition compression, not ceremony.'). Rewarding brevity that preserves clarity, this matches the 'lean and efficient; every token earns its place' anchor. | 5 / 5 |
Actionability | The 10-step Procedure gives concrete, executable process guidance: named paths ('../../references/routing-map.json'), naming rules, and a Validation section with specific gates ('skill_gate.py', 'Vale', 'skill_gate ... progressive-disclosure lint') plus example user asks. It stops short of 5 because there is no concrete sample artifact or command invocation, and several steps remain policy-level ('Compress conclusions to decisions that change routing, deletion, investment...') without showing how. | 4 / 5 |
Workflow Clarity | The Procedure is a clearly sequenced 10-step workflow with explicit validation checkpoints ('record each gate as pass, fail, or blocked'), an error-recovery feedback loop ('Rerun failed gates'), preconditions, and a dedicated Failure Mode section with stop/pivot conditions. This matches the anchor for clear sequence with explicit validation steps and feedback loops. | 5 / 5 |
Progressive Disclosure | The body is an overview that routes mode-specific detail to one-level-deep reference files via a well-signaled References section with 'Read when <condition> -> <path>' routing, and locally referenced files (references/contract.yaml, references/evals.yaml, references/strategy-output-contract.md) exist in the bundle. It is not 5 because most referenced paths ('../../references/...') point outside the bundle where their existence cannot be verified, and the body still inlines considerable policy detail (Constraints, Gotchas, Anti-Patterns, Stage Arc Boundary) that could arguably be routed to references. | 4 / 5 |
Total | 18 / 20 Passed |