Content
81%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 strong, tight instruction skill: concrete commands and a real-API template, an explicitly validated workflow with feedback loops and a final checklist, and clean organization with no padding. Weaknesses are minor — a few trimmable rationale sentences and placeholder-filled code in the scenario template.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Dense and prescriptive with no explanation of concepts Claude already knows — the anti-pattern list, principles, and table all carry specific instruction. Only minor trimmable passages remain, e.g., the opening rationale "it says things are fine, it costs time to run and maintain, and it breaks on harmless refactors" and refactor-breakage being stated in both the anti-pattern list and the principles. | 4 / 5 |
Actionability | Provides copy-paste run commands ("cd packages/core && npx vitest run src/loop/test-utils/aimock/scenarios/<name>.scenario.test.ts"), a near-complete scenario template using the real API (describeForAllEngines, runLoopScenario, sequenceIndex fixtures), and a table mapping areas to shared suites. Minor gaps: the template uses "'...'" placeholders and defers the full API to the repo README. | 4 / 5 |
Workflow Clarity | The numbered principles follow the test lifecycle (design → reproduce → verify → cover paths → consolidate) with explicit validation loops — "Run it against the pre-fix commit... and confirm it fails on the assertion you mean", "break the behavior on purpose and confirm the new test fails", "run them 20–40 times" — plus a final "Before you finish" checklist of checkpoints. | 5 / 5 |
Progressive Disclosure | Well-organized sections with clear headers, a compact area-to-suite table, and one well-signaled external pointer ("Read packages/core/src/loop/test-utils/aimock/README.md for the full API"). No bundle files exist; ~45 lines of aimock operational detail are inlined, which is acceptable at this size but is the main organization gap versus the fully-split anchor 5. | 4 / 5 |
Total | 17 / 20 Passed |