BD skillguard
Security scanner for ClawHub skills. Vet third-party skills before installation — detect dangerous patterns, suspicious code, and risky dependencies.
Security scanner for ClawHub skills.
As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, failures and branches
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 7
✓ No critical or high findings
Medium and low: 7
-
low Risky intent
intent-offensive-securitySKILL.md:26Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| **Access your filesystem** | Data theft, ransomware |
-
low Dangerous commands
cmd-privilegeSKILL.md:93Privilege escalation / world-writable permissions (documentation table row; documentation of a security skill)| **Privilege Escalation** | `sudo`, `setuid`, `chmod 777` | Root access |
tablesecurity skill -
low Risky intent
intent-offensive-securitySKILL.md:93Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| **Privilege Escalation** | `sudo`, `setuid`, `chmod 777` | Root access |
-
low Risky intent
intent-offensive-securitySKILL.md:94Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| **Reverse Shell** | Socket + subprocess patterns | Remote access |
A further 3 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- 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 rating: all ten parameters 48/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 40Consistency. Frontmatter name (skillguard) differs from the folder (clawscan)
- 60Tools and files. Uses tools (bash, web, python, node) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 25 steps
- 100Execution cost. Instruction body is 3188 tokens
- 100Progress reporting. Reports progress
- low 15 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 tags): a typed call is more reliable
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)
- +3Output format is not stated: the model decides each time
- -227 emoji in the instructions: noise for the model
- +2Single-language instructions
- +3Description length 149: enough signal without eating the budget
- +4Structure: 34 headings
- +3Step-by-step instructions: 25 items
- +4Has examples (18 code blocks)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.