Loading the registry…
Read a partner's agent codebase end-to-end and produce a polished assessment report that names concrete weaknesses with file-level evidence, threads Ratel-relevant findings through the report, and ends with conditional pointers to the right follow-up skills. Static-only by default; if a Langfuse project is already wired and reachable via MCP, pull a small live sample to enrich findings (graceful degrade if not). Use whenever the user wants a first-touch review of a partner agent, asks "assess our agent", "review our agent", "audit this agent", "where can we improve", "what would Ratel notice in this codebase", "give us an honest read of our agent", or invokes `/ratel-assessment`. Trigger on phrases like "look at this agent and tell us what's weak", "we want a Ratel-flavored review", "first-pass audit before we engage", "spot the low-hanging fruit in this repo" — even if the user doesn't say "skill" or "ratel-assessment" by name. This skill writes a markdown report; it does not edit the agent code itself.
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.
274 critical findings reported by 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 -- ratel-assessment
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- ratel-assessment ~/.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.7s
v2.0.11
23 findings · 10.3s
v0.3.26
290 findings · 1.5s
v0.1.0
0 findings · 4.2s
v0.1.0
1 finding · 4.2s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
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 314 findings above stand exactly as their scanners reported them, at full severity.