Content
80%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 efficient, well-structured internal reference that communicates invariants through concrete named symbols and a regression test list. Its only real weakness is that it is a rule set rather than a sequenced workflow, so workflow clarity is merely adequate.
Suggestions
Add a short numbered 'Adding a new harness' sequence (declare mapping in agentcfg → verify via TestReplayPinsCandidateModelAndEffortOnTheHarness) to lift workflow clarity above 3.
Include one worked before/after example of mapping a model+effort request to a harness's native flags to make the actionability fully copy-paste ready.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean, dense reference prose with no padding and no explanation of concepts Claude already knows; every token earns its place and it assumes full competence. | 5 / 5 |
Actionability | Provides concrete, actionable directives with named symbols ('agentcfg', 'agent.NewWithOptions', 'agentcfg.ServedMatchesRequested') and explicit do/don't rules, but lacks worked examples showing exactly how to add a new harness end-to-end. | 4 / 5 |
Workflow Clarity | The body is a set of architectural invariants rather than a sequenced workflow; the 'Regressions' bullet supplies an implicit verification checkpoint, but there is no explicit ordered process with validation steps. | 3 / 5 |
Progressive Disclosure | Under 50 lines, well-organized into focused bullets, self-contained, with a single clearly signaled one-level-deep reference link to eval.md — meeting the simple-skill exception for a top score. | 5 / 5 |
Total | 17 / 20 Passed |