Content
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a well-structured routing/compatibility layer with clear sequencing, explicit stop conditions, and good safety boundaries. Its main weaknesses are moderate verbosity from overlapping sections (Constraints, Execution Boundaries, Failure Mode) and a lack of truly executable/concrete guidance—most steps reference abstract contracts or delegations rather than specific commands. The output template is a strong concrete element that anchors the otherwise abstract procedure.
Suggestions
Consolidate overlapping sections (Constraints, Execution Boundaries, Failure Mode) into a single 'Safety & Boundaries' section to reduce redundancy and improve token efficiency.
Make procedure steps more actionable by specifying exactly how to 'run the phase gate contract' or 'delegate to he-work'—e.g., include the actual invocation pattern or tool call format rather than abstract references.
Remove the Philosophy section or fold its single key insight ('heartbeat does not authorize implementation') into the procedure as a constraint, since Claude can infer the routing purpose from context.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some redundancy—execution boundaries largely restate constraints, and several sections (Failure Mode, Gotchas, Validation Gates) overlap in content. Some sections like 'Philosophy' explain routing concepts Claude could infer from the procedure itself. | 2 / 3 |
Actionability | The procedure provides a clear sequence of steps and the output template gives a concrete YAML example, but there are no executable code/commands—steps like 'run the phase gate contract' and 'delegate to he-work' are abstract references to other processes rather than concrete, copy-paste-ready instructions. | 2 / 3 |
Workflow Clarity | The procedure is clearly sequenced (steps 1-6) with explicit validation checkpoints (step 3 blocks on stale evidence, step 6 is a hard stop boundary), a fail-fast policy in Validation Gates, and a clear failure mode that returns blocked status and names recovery steps. The feedback loop of 'stop at first failed gate' is well-defined. | 3 / 3 |
Progressive Disclosure | References to external contracts and files are listed at the bottom with clear paths, and the Stage Arc Boundary section references an external contract appropriately. However, without bundle files to verify these references exist, and with some inline content (like the full Stage Arc Boundary explanation) that could be deferred to the referenced contract, the disclosure structure is adequate but not optimal. | 2 / 3 |
Total | 9 / 12 Passed |