BC security-audit
Comprehensive security auditing workflow covering web application testing, API security, penetration testing, vulnerability scanning, and security hardening.
Comprehensive security auditing workflow covering web application testing, API security, penetration testing, vulnerability scanning, and security hardening.
As a process C 64/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches
The same skill appears in 3 more places: agentic-awesome-skills, agentic-awesome-skills, RA-Skills
How to improve
- 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Risky intent
intent-offensive-securitySKILL.md:3Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)description: "Comprehensive security auditing workflow covering web application testing, API security, penetration testing, vulnerability scanning, and security hardening."
quoted -
low Risky intent
intent-offensive-securitySKILL.md:14Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Comprehensive security auditing workflow for web applications, APIs, and infrastructure. This bundle orchestrates skills for penetration testing, vulnerability assessment, security scanning, and remed
-
low Risky intent
intent-offensive-securitySKILL.md:125Offensive-security / dual-use content (legitimate for authorised testing; review intended use)### Phase 5: Penetration Testing
-
low Risky intent
intent-offensive-securitySKILL.md:128Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)- `pentest-commands` - Penetration testing commands
quoted -
low Risky intent
intent-offensive-securitySKILL.md:129Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)- `pentest-checklist` - Pentest planning
quoted
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "risk" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "date_added"
Process rating: all ten parameters 64/100
- 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
- 30Running it twice. 1 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 96 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1309 tokens
- 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 157: enough signal without eating the budget
- +4Structure: 37 headings
- +3Step-by-step instructions: 96 items
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.