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.
An unusually disciplined instruction-only skill: every token is a rule, the phase sequence is gated with explicit authorization and stop conditions, and the progressive disclosure is exemplary — every reference is conditionally loaded and verified present. The residual costs are minor: a duplicated seeing/driving explanation, a few over-compressed sentences, and operational detail that lives entirely in references.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense, imperative, and assumes Claude's competence with zero padding, but the seeing-vs-driving distinction is stated twice (intro paragraph and again under "Build it") and a few sentences are contorted enough to cost re-reading ("the offer to add that line comes before the root is resolved, or accepting it cannot help this run"). Not 5 because that repetition and tangling means not every token earns its place; well above 3 since nothing explains concepts Claude already knows. | 4 / 5 |
Actionability | Concrete, executable specifics are present: exact run paths (`.context/compound-engineering/ce-prototype/<date>-<slug>/` with a `/tmp` fallback), a literal probe command (`git -C <repo root> check-ignore -q .context/compound-engineering/` with the trailing-slash caveat), and the named `decisions.md` capsule. Not 5 because much operational detail is delegated to references and some inline guidance stays abstract ("speak only when they can act on something new, in one short line naming what happened"); instruction-only framing keeps it at 4 rather than lower. | 4 / 5 |
Workflow Clarity | A clear Scope → Build → Keep the decisions → Apply sequence with explicit gates ("Do not build until authorized", the no-human stop, the gitignore probe before root resolution) and an undo/recovery path for the risky overlay case ("restore only the files you changed. If you cannot undo them cleanly, name the files you left modified"). Not 5 because several checkpoints (go-ahead message, annotation-loop pacing) live in references rather than inline and some validation is implicit ("Update the capsule when you are confident"). | 4 / 5 |
Progressive Disclosure | The ~53-line body is a genuine overview: six reference files, all verified to exist, each with an explicit load condition — including when NOT to load one ("A question settled by driving does not load it") — plus bundled `scripts/light-webserver.js` and `assets/annotate.*` used via a SKILL_DIR anchor. References are one level deep, pointing only to siblings and bundled files, never to deeper content. This matches the clear-overview, well-signaled, one-level-deep anchor. | 5 / 5 |
Total | 17 / 20 Passed |