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 -- devops_bootcamp_training
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- devops_bootcamp_training ~/.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
10 findings · 1.9s
v2.0.11
Timed out
0 findings · 300.0s
v0.3.74
Timed out
0 findings · 450.0s
v0.1.0
Timed out
0 findings · 300.0s
v0.1.0
Timed out
0 findings · 300.0s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.3s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 2.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 22, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner ·!: timeoutagent-audit-kit ·!: timeoutnerlo-behavioral ·!: timeoutnerlo-install-instruction ·!: timeoutcapslock ·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 10 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.
4 Agent instruction file — The match is in a file that instructs an AI coding agent — a CLAUDE.md or similar. It is documentation of intent, and our own check confirmed it is not part of what gets installed.
Rules: permissions-no-deny-list, hooks-no-pretooluse · Files: docs/ai-transformation-core-docs/AIOS AI Operating System/.claude/settings.json, docs/ai-transformation-core-docs/plugins/aios-ai-operating-system/source/.claude/settings.json · reported by agentshield
2 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: hooks-code-context-output-18 · Files: docs/ai-transformation-core-docs/AIOS AI Operating System/hooks/validate_output.py, docs/ai-transformation-core-docs/plugins/aios-ai-operating-system/source/hooks/validate_output.py · reported by agentshield
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.
2 hooks-no-pretooluse
Files: settings.local.json, .claude/settings.local.json · reported by agentshield
2 permissions-no-deny-list
Files: settings.local.json, .claude/settings.local.json · reported by agentshield
Artifact has broad permissions in configuration files.
The artifact's configuration files, specifically `.claude/settings.local.json` and `settings.local.json`, contain settings that permit broad capabilities. These settings do not restrict the artifact's actions, which could lead to unintended operations. This includes potential for network egress, shell execution, credential access, or file writes, depending on how these permissions are utilized by the artifact's logic.
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.