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.
5 critical findings reported by cisco-skill-scanner. 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 -- 'kitsada-007/claude-skille (go-dev)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'kitsada-007/claude-skille (go-dev)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
6 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
2 findings · 0.7s
v2.0.11
17 findings · 6.1s
v0.3.74
0 findings · 0.8s
v0.1.0
0 findings · 3.0s
v0.1.0
0 findings · 3.0s
vv0.3.2
Incomplete run
0 findings · 0.4s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 0.9s
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: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·!: incompletenerlo-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 19 findings across every scanner that examined this package. None of the 5 findings rated critical by their scanner were dismissed.
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.
5 COMMAND_INJECTION_JS_CHILD_PROCESS
Files: /repo/.claude/statusline.js · reported by cisco-skill-scanner
4 MANIFEST_MISSING_LICENSE
Files: /repo/.claude/skills/go-dev/SKILL.md, /repo/.agents/skills/go-dev/SKILL.md, /repo/.claude/SKILL.md and 1 more · reported by cisco-skill-scanner
3 DATA_EXFIL_JS_FS_ACCESS
Files: /repo/.claude/statusline.js · reported by cisco-skill-scanner
2 MANIFEST_INVALID_NAME
Files: /repo/.agents/SKILL.md, /repo/.claude/SKILL.md · reported by cisco-skill-scanner
2 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/.claude/SKILL.md, /repo/.agents/SKILL.md · reported by cisco-skill-scanner
1 hooks-no-pretooluse
Files: settings.json · reported by agentshield
1 LOW_ANALYZABILITY
Files: /repo/.claude · reported by cisco-skill-scanner
1 permissions-no-block
Files: settings.json · reported by agentshield
Artifact has critical command injection and data exfiltration risks.
The artifact exhibits critical command injection vulnerabilities in `/repo/.claude/statusline.js`, allowing shell execution. It also has high-severity data exfiltration risks from file system access within `/repo/.claude/statusline.js`. Additionally, the artifact's analyzability is low, and it has medium-severity issues related to permissions and hooks. These findings indicate potential for unauthorized system access and data exposure.
Concern level assessed by the review: Critical. 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.