Loading the registry…
Teaches how to write acceptance criteria that are unambiguous, testable, and complete — and, per Ken Pugh's Acceptance Test-Driven Development (ATDD) practice, how criteria are derived: from a concrete worked example first (via example-mapping), never decided as an abstract rule and illustrated afterward. Covers the Gherkin Given/When/Then format, the rule-based format, how to handle edge cases and negative scenarios, and how acceptance criteria connect directly to BDD feature files. Includes scripts/scaffold-criteria.sh (generates a new criteria doc pre-filled with story metadata) and scripts/validate-criteria.sh (mechanically checks testability, Golden Triangle coverage, and a traceable Derived-From link). Acceptance criteria are the primary handoff from the requirements-analyst to the test-strategist. Used during the Ideate phase after user stories are written and example maps are discovered.
Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
325 critical findings reported by cisco-skill-scanner, agent-audit-kit, 7 of them in the installed artifact. The composite score alone does not reflect this — read the per-scanner reports below.
Claude Skills install to a single target, no runtime picker.
nerlo install -- acceptance-criteria
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- acceptance-criteria ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
5 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v1.4.0
13 findings · 0.8s
v2.0.11
689 findings · 64.3s
v0.3.26
466 findings · 17.0s
v0.1.0
0 findings · 8.4s
v0.1.0
37 findings · 8.4s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.2s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image, nerlo-multi-source.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 13, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicable | rejected |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
This review has not run for this scan yet. It runs once per scan, in the background, and is kept; it appears here when it has. Until then all 1,205 findings above stand exactly as their scanners reported them, at full severity.