Content
86%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 well-structured, actionable test-writing guide with excellent progressive disclosure and concise tables. Its main gap is the absence of an explicit test-verification checkpoint in the workflow.
Suggestions
Add a final workflow step instructing Claude to run the test (e.g., `jest <path>`) and confirm it passes for the right reason / fails for the right reason, to close the verification gap.
In the Version Detection section, show the exact package.json field check (e.g., grep `@testing-library/react-native` version) so the branching step is fully executable.
Tighten the opening italic disclaimer to one line so it stays lean while retaining the don't-trust-memorized-APIs warning.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly lean tables, terse rules, and minimal prose with no generic concept padding; the opening version-accuracy disclaimer is slightly more than minimal but is load-bearing for this API-version-sensitive skill, so it sits just below a 5. | 4.5 / 5 |
Actionability | Copy-paste-ready code blocks for userEvent, fireEvent, render wrappers, waitFor, and fake timers, plus concrete tables of matcher and role signatures, match the fully-executable anchor. | 5 / 5 |
Workflow Clarity | Version Detection and Query Priority give a clear sequence, but there is no explicit verification checkpoint (e.g., run the test and confirm it passes/fails for the right reason), leaving a validation gap between anchors 3 and 4. | 3.5 / 5 |
Progressive Disclosure | The body is an overview pointing to one-level-deep, clearly signaled reference files (v13, v14, anti-patterns) that all exist on disk, with easy navigation via the Version Detection and References sections. | 5 / 5 |
Total | 18 / 20 Passed |