Content
78%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-structured, directive planning skill with concrete thresholds, checklists, feedback loops, and exemplary one-level-deep progressive disclosure. The body is efficient but carries a few rhetorical sentences and abstract directives that keep conciseness, actionability, and workflow_clarity just under full marks.
Suggestions
Trim rhetorical justification sentences (e.g. the "discards the iterations someone else already paid for" line) to pure directives to lift conciseness toward 5.
Add one short worked example of a completed approved-plan output with filled-in fields, so abstract directives like "deform the design to survive its failure" have a concrete, copy-paste-ready reference and improve actionability.
Open with a single numbered core sequence (preflight → check official solutions → propose → validate → simplicity gate → handoff) so the mode-based sections hang off one explicit ordering and improve workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean and directive with concrete thresholds (8 files, 3 components), but a few rhetorical justification sentences (e.g. "First-principles design next to a proven implementation discards the iterations someone else already paid for.") could be trimmed to pure directives, keeping it just below the lean-every-token-earns-its-place anchor. | 4 / 5 |
Actionability | Guidance is largely concrete (specific thresholds, a defined Output template, named rules), but several directives stay abstract ("deform the design to survive its failure", "state what evidence would change it"), which is actionable guidance rather than fully copy-paste-ready steps. | 4 / 5 |
Workflow Clarity | There is a clear progression with checkpoints and checklists (Validate Before Handoff, red-flags self-check, Simplicity Gate, approval gates) plus feedback loops, but the flow is organized as conditional modes/gates rather than one explicit linear numbered sequence, leaving minor sequencing gaps. | 4 / 5 |
Progressive Disclosure | The body is a clear overview that points to three well-signaled one-level-deep reference files (durable-context.md, mode-evaluation.md, mode-triage.md), each stating when to load it; all referenced files exist and contain no nested references, matching the clear-overview anchor. | 5 / 5 |
Total | 17 / 20 Passed |