Content
77%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.
The content is a tight, well-sequenced workflow with copy-paste commands, explicit exit-code validation, and recompile feedback loops. Its main defects are bundle references that do not resolve (docs/WORKFLOW.md, docs/DESIGN.md, and the referenced template/script paths) and repeated compiler-disclaimer statements that could be consolidated.
Suggestions
Ship docs/WORKFLOW.md and docs/DESIGN.md in the bundle (or remove/inline those links) so the referenced navigation paths resolve.
Include the referenced template and compile script (templates/contribution-review-observation.json, scripts/compile_contribution_review.py) in the bundle, or state where they live relative to the checkout.
Consolidate the four repeated compiler-disclaimer statements into a single "What the compiler does not do" note to reduce token overhead.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean with no explanations of known concepts, but the compiler's non-responsibility is restated roughly four times ("it does not independently inspect Git, files, CI, test results, coverage, or referenced evidence"; "The compiler does not execute them"; "It does not prove that supplied claims are true or CI passed"; "never approves a contribution") — minor over-explanation that could be consolidated, matching anchor 4 rather than the every-token-earns-its-place anchor at 5. | 4 / 5 |
Actionability | The compile step is fully executable ("mkdir -p .memory-kit", "cp skills/ecc-contribution-review/templates/... ", "python3 skills/ecc-contribution-review/scripts/compile_contribution_review.py ... --output ...") with explicit exit-code semantics ("Exit code 0 means a packet was emitted... Exit code 2 means validation faults"). However, steps 1-4 direct recording observations without any gathering commands, and the referenced template/script paths are absent from the bundle, matching "mostly executable guidance with minor gaps" rather than the fully copy-paste-ready anchor at 5. | 4 / 5 |
Workflow Clarity | Seven clearly numbered steps include explicit validation checkpoints ("Run the required validators and tests separately. Record exact commands, results, and evidence"; "Review every reported contradiction and semantic page fault"; exit codes 0/2 with "Inspect the packet and stderr") and a recompile feedback loop ("Recompile after changes to HEAD, policy, manifests, catalog, adapters, tests, coverage, security findings, or review evidence") — matching the anchor 5 pattern of explicit validation with error-recovery loops. It is not 4 because validation and recovery are explicit rather than implied. | 5 / 5 |
Progressive Disclosure | The body is a concise overview with clearly signaled one-level-deep references ("See [the workflow](docs/WORKFLOW.md), [the design](docs/DESIGN.md), and [the contract](references/contribution-review-contract.md)"), but only references/contribution-review-contract.md actually exists in the bundle — docs/WORKFLOW.md and docs/DESIGN.md are absent, so two of three references dead-end. Scoring against the actual bundle structure, unresolved references are more than a minor organization gap, keeping this at anchor 3 rather than 4. | 3 / 5 |
Total | 16 / 20 Passed |