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.
This is a well-crafted instruction skill: a clearly sequenced five-step procedure with explicit stop conditions and validation checkpoints, concrete report and ticket formats, and a genuinely useful trust-boundary section. The main improvable areas are trimming the motivational intro and provenance footer, and splitting the report/matrix format detail into a reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with instructive content ("Record what you observed, not what you expected to observe", "A finding without evidence is an opinion") and assumes Claude's competence — it never explains concepts like browsers or APIs. Minor instances could be trimmed: the three-paragraph motivational intro and the provenance footer add tokens that do not guide execution, placing it just below the lean 5 anchor. | 4 / 5 |
Actionability | Gives concrete, executable direction: "Diff the branch against the trunk it will merge into", "One row per (persona, journey, assertion) triple, written before anything is launched", a specified report location ("docs/dogfood-reports/, named for the branch and the date") with its required contents, and enumerated ticket fields, plus a worked positive/negative phrasing example ("upload a file, then share it with a colleague" — not "POST /files then PATCH /acl"). Not 5 because the mechanics of actually driving each surface (browser automation, tool-client invocation) are left unspecified, an acknowledged consequence of being product-agnostic. | 4 / 5 |
Workflow Clarity | Five clearly sequenced steps with explicit validation checkpoints and error-recovery loops: stop if the product article is missing or unfilled ("Guessing a persona produces a report about an imaginary user"), stop on a red suite ("If the tests are failing, the branch is not ready to be dogfooded"), capture startup output for later diagnosis, and "If the surface will not come up, that is the finding, and the run stops here". The pre-written matrix functions as a checklist, matching the 5 anchor's pattern of explicit validation steps and feedback loops. | 5 / 5 |
Progressive Disclosure | A well-sectioned single file whose external references ("constitution/local-product.md.template", "/to-tickets", the LICENSE provenance file) are one level deep and clearly signaled, with no bundle files present and no nested reference chains. Not 5 because at ~144 lines it exceeds the simple-skill exception, and detail like the report/ticket format and matrix construction (~30 lines) is kept inline where a reference file could carry it. | 4 / 5 |
Total | 17 / 20 Passed |