Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nwave-ai/nw-dr-review-criteria
Critique dimensions, severity framework, verdict decision matrix, and review output format for documentation assessment reviews
Passed 20 of 21 test cases with the skill, and 11 of 21 without it.
and 10 more in the full report
10 fixed11 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
The document `/docs/user-management.md` was assessed. The secondary audit calculates that document content purity is 65% due to extensive content drift across multiple user needs. What recommended verdict must be recorded in `verdict_review`?
| Checked | Without skill | With skill |
|---|---|---|
| Sets recommended_verdict to Restructure Required. | Missed | Passed |
The instructions your model reads when the skill loads.
Verify type assignment against DIVIO decision tree.
Questions: Do cited signals support assigned type? | Contradicting signals ignored? | Confidence appropriate? | Decision tree leads to same classification?
Verification: 1) Run decision tree independently 2) Check positive signals present 3) Check for red flags 4) Verify confidence matches signal strength
Severity: if wrong classification leads to wrong verdict = blocking.
Verify all type-specific criteria checked. Questions: All items checked? | Pass/fail correct? | Issues properly located? | Any criteria missed?
Tutorial (required): completable without external refs | steps numbered/sequential | verifiable outcomes | no assumed knowledge | builds confidence
How-to (required): clear goal | assumes fundamentals | single task | completion indicator | no basics teaching
Reference (required): all params documented | return values | error conditions | examples | no narrative
Explanation (required): addresses "why" | context/reasoning | alternatives considered | no task steps | conceptual model
Verify all five anti-patterns checked with accurate findings.
Verification: independently scan, count lines per quadrant, compare to documentarist's findings, flag discrepancies.
Criteria: Specific (exact what/where) | Actionable (author knows next step) | Prioritized (important first) | Justified (why it matters) | Root cause (underlying issue)
Bad: "Improve the documentation", "Make it clearer" Good: "Move explanation in section 3.2 (lines 45-60) to separate doc", "Add return value docs for login()"
test cases passed, vs 11 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.