Loading the registry…
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 -- 'fribnd/ensdf-agent (adopted-vs-individual-dataset-comparison)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'fribnd/ensdf-agent (adopted-vs-individual-dataset-comparison)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
4 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
49 findings · 11.0s
v0.3.74
1 finding · 3.5s
v0.1.0
0 findings · 4.4s
v0.1.0
0 findings · 4.4s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
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
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-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.
Out of 50 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 49 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
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.
1 CI or editor configuration — The match is in build, CI or editor configuration, confirmed by our own check to be outside the installed artifact.
Rules: FILE_MAGIC_MISMATCH · Files: /repo/.github/plugin/marketplace.json · reported by cisco-skill-scanner
49 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: RESOURCE_ABUSE_INFINITE_LOOP, FILE_MAGIC_MISMATCH, AAK-SKILL-002 and 3 more · Files: /repo/plugins/ensdf-agent/scripts/angular_momentum_coupling.py, /repo/.claude-plugin/marketplace.json, plugins/ensdf-agent/skills/editorial-review-guidelines/SKILL.md and 36 more · reported by cisco-skill-scanner, agent-audit-kit
Critical security risks in multiple scripts
The artifact contains critical security findings in Python scripts such as `validate_ens.py`, `Java_FormatCheck.py`, `compare_line_metrics.py`, and `ens2pdf.py`. These findings, identified by the 'bearer' scanner, indicate potential vulnerabilities that warrant immediate attention. Additionally, high-severity findings suggest risks like resource abuse in scripts and potential insecure configurations.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Showing 1 of 1; the rest are in the per-scanner reports above.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.