B skillscanner
Security scanner for ClawHub skills from Gen Digital. Looks up skill safety via the scan API.
Security scanner for ClawHub skills from Gen Digital.
B
87/100
Overall score
- Safety 60%
- Quality 40%
- Tests bonus
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): it is the main trigger signal.
- Add evals/evals.json with 4–6 real requests and expected answers: the full check will then use your cases instead of a model draft.
- Add a spec.yaml with triggers and assertions (skilltest init): the behaviour contract for CI.
Guard findings · 1
✓ No critical or high findings
Medium and low: 1
-
low Risky intent
intent-offensive-securitySKILL.md:75Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| **Access your filesystem** | Data theft, ransomware |
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Lint
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "keywords" - note
frontmatter-keyunknown frontmatter key "triggers"
Process maturity 53/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 10 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 772 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 93: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Structure: 6 headings
- +3Step-by-step instructions: 10 items
- +4Has examples (2 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.