Loading the registry…
Performs deep static analysis of a codebase to generate a comprehensive, hierarchical, cross-referenced documentation ecosystem. Use this skill whenever the user wants to analyze, document, understand, or audit a codebase — even if they phrase it as "document my project", "analyze the repo", "generate docs", "audit technical debt", "understand this codebase", or "create documentation for this code". This skill covers: program structure extraction, architectural documentation, behavioral analysis, technical debt identification, dependency mapping, and migration planning. Always use this skill before exploring a codebase for documentation purposes — it tells you exactly how to approach the analysis and what to produce. Triggers: "analyze codebase", "document the project", "create docs", "audit tech debt", "understand this repo", "generate documentation", "what's the architecture", "map the code", "analyze dependencies", "find outdated components", "technical debt report".
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.
1011 critical findings reported by cisco-skill-scanner, agent-audit-kit, 0 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 -- codebase-analysis
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- codebase-analysis ~/.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
0 findings · 0.8s
v2.0.11
1089 findings · 62.0s
v0.3.26
73 findings · 34.5s
v0.1.0
0 findings · 33.9s
v0.1.0
6 findings · 33.9s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 11.0s
No report in this scan: capslock, govulncheck, osv-scanner, trivy, trivy_image.
2 scans on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 3, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completenerlo-multi-source ·n/a: not applicable | rejected |
| Jul 31, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completenerlo-multi-source ·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,168 findings above stand exactly as their scanners reported them, at full severity.