find-skills
No security findings. Scanned 1 time, most recently 2026-02-06.
Second scanner: NVIDIA SkillSpector
Independent static run, no language model, over the same files as the Cisco scan above. How the two scanners compare across the whole corpus: Two scanners, one corpus.
What this skill does
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
- Package
- 1 file, 4.5 KB
- SKILL.md
- 654 words, 11 sections
- Code
- None. Instructions only.
SKILL.md covers: Find Skills · When to Use This Skill · What is the Skills CLI? · How to Help Users Find Skills · Step 1: Understand What They Need · Step 2: Search for Skills · Step 3: Present Options to the User · Step 4: Offer to Install · Common Skill Categories · Tips for Effective Searches · When No Skills Are Found
Findings
No findings. SAFE
What is in the package
| File | Kind | Size |
|---|---|---|
SKILL.md | doc | 4.5 KB |
External hosts referenced
skills.sh
Hostnames that appear in the skill's files. Referencing a host is not a finding; compare against the findings above and the skill's stated purpose.
Package contents recorded 2026-10-22. The scan above ran against the version current at scan time; the two can differ if the skill has since been updated.
What we checked
- Static analyzer. Pattern rules over SKILL.md and bundled files: known-bad commands, exfiltration URLs, secrets, obfuscation.
- Behavioral analyzer. Checks what the skill asks the agent to do against what its description claims it does.
- Llm analyzer. A language model reads the skill and reports intent-level issues the rules cannot express.
- Trigger analyzer. Looks for instructions that fire on conditions the user did not ask for.
- Meta analyzer. A second model pass that validates, deduplicates and re-scores the other analyzers' findings.
What we did not check
- Runtime behaviour. The skill was not executed; findings come from reading its files.
- Anything fetched at install or run time, including remote scripts, package dependencies, and URLs the skill tells the agent to open.
- Content the analyzers cannot read: images, binaries, and some non-English text.
- Known scanner bypass classes. See the methodology and limitations page.
Sources
- Repository: https://clawhub.ai/skills/find-skills
- Raw scan result: find-skills-scan.json
- Badge for your README:
- Request a re-scan