DB normieclaw-security-team
(no description)
Not recommendedlow grade D
As a process B 69/100 · Nearly there — weak spots: when it triggers, inputs and preconditions
How to improve
- Add a description to the frontmatter: without it the skill never triggers.
For the model run — optional
- 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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Risky intent
intent-offensive-securitySECURITY.md:23Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- ✅ **No elevated permissions required.** All scripts run as the current user. No `sudo`, no root, no privilege escalation.
-
low Dangerous commands
cmd-privilegeSKILL.md:46Privilege escalation / world-writable permissions (negated — the text forbids it)3. **File Permissions:** Check that `.env`, config files, and key directories don't have overly permissive modes (no `chmod 777`, no world-readable sensitive files). Use `stat` to read permissions.
negated
A further 1 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 14. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
frontmatterSKILL.md: no YAML frontmatter block found - error
name-missingSKILL.md: frontmatter has no `name` - error
description-missingSKILL.md: no `description` — the skill can never trigger
Process rating: all ten parameters 69/100
- 30When it triggers. No condition that starts the skill
- 30Inputs and preconditions. Does not say what the process needs to start
- 60Tools and files. Uses tools (bash, web, git) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 4113 tokens
- 100Steps. 82 steps
- 100Failures and branches. 14 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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 0: 120–800 characters recommended
- -2localhost URLs: will not work for another user
- -217 emoji in the instructions: noise for the model
- +2Single-language instructions
- +4Structure: 21 headings
- +3Step-by-step instructions: 82 items
- +3Output format is stated explicitly
- +4Has examples (6 code blocks)
- +3All 2 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.
External checks
ClawHub: suspicious
This is a coherent security-audit skill, but it asks for broad local scanning, persistence, and network-capable checks while overstating its read-only and local-only behavior.
LLM: suspicious (high) · VirusTotal: · 29 May 2026