Loading the registry…
Use when documenting how an application works — writing or refreshing a technical reference doc per part of the system (what it does, its data model, API, events, configuration, gotchas), deriving end-user or operator guides from those docs, or auditing existing docs for drift against the code. Trigger this whenever the user asks to document an app or a module, explain in writing how a system works, onboard someone new to a codebase, write a user guide / operator manual / admin handbook, or check whether the docs still match the code — including when they describe the job without using the word "documentation" ("someone new needs to understand this", "write up how the approvals thing works", "we need something to hand to customers").
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.
Claude Skills install to a single target, no runtime picker.
nerlo install -- 'warwickschroeder/repo-standards (app-documentation)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'warwickschroeder/repo-standards (app-documentation)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
3 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.
v2.0.11
36 findings · 9.2s
v0.3.74
5 findings · 1.3s
v0.1.0
0 findings · 3.1s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
v0.1.0
No source files this scanner can analyze were found in this artifact. What each scanner covers
0 findings · 3.1s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.1s
v0.71.0
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.2s
v2.3.8
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.2s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 21, 2026 | Flagged51 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral ·n/a: not applicablenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy ·n/a: not applicableosv-scanner ·n/a: not applicabletrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
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.
Out of 41 findings across every scanner that examined this package.
Two keys had to turn. The model had to name a reason from a fixed list of six, and a deterministic check of ours — over which files this artifact actually installs — had to independently agree. Anything it could not corroborate is in “not reviewed” above, at full severity.
2 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: /repo/docs/plans/SKILL.md · reported by cisco-skill-scanner
These findings are in files this artifact installs and are not placeholder values. No false-positive basis can be corroborated for such a finding, so this review never dismisses one; they were not sent to the model and stand at their scanner's severity.
14 MANIFEST_MISSING_LICENSE
Files: /repo/plugins/smoke-tests/skills/smoke-tests/SKILL.md, /repo/plugins/regression-runbooks/skills/regression-runbooks/SKILL.md, /repo/plugins/app-documentation/skills/app-documentation/SKILL.md and 11 more · reported by cisco-skill-scanner
12 FILE_MAGIC_MISMATCH
Files: /repo/plugins/regression-runbooks/skills/regression-runbooks/template-runbook.md, /repo/plugins/app-documentation/skills/app-documentation/template-user-guide.md, /repo/plugins/modular-monolith/skills/modular-monolith/template-gap-report.md and 1 more · reported by cisco-skill-scanner
7 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/Blueprints/SKILL.md, /repo/plugins/smoke-tests/SKILL.md and 4 more · reported by cisco-skill-scanner
4 AAK-MARKETPLACE-001
Files: .claude-plugin/marketplace.json · reported by agent-audit-kit
1 AAK-HEALTHCARE-AI-004
Files: plugins/regression-runbooks/skills/regression-runbooks/reference.md · reported by agent-audit-kit
1 MANIFEST_INVALID_NAME
Files: /repo/Blueprints/SKILL.md
High-severity marketplace configuration issues detected.
The artifact exhibits high-severity issues related to its marketplace configuration, specifically within `.claude-plugin/marketplace.json`. These findings indicate potential risks in how the artifact interacts with its environment or handles its own metadata. Additionally, multiple files have magic number mismatches, suggesting content that does not align with expected file types, and a healthcare-specific AI rule was triggered.
Concern level assessed by the review: High. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.