AB Pentest Checklist
This skill should be used when the user asks to "plan a penetration test", "create a security assessment checklist", "prepare for penetration testing", "define pentest scope", "follow security testing best practices", or needs a structured methodology for penetration testing engagements.
This skill should be used when the user asks to "plan a penetration test", "create a security assessment checklist", "prepare for penetration testing"…
As a process B 72/100 · Nearly there — weak spots: result and completion, consistency, running it twice
The same skill appears in 1 more place: 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:2Offensive-security / dual-use content (legitimate for authorised testing; review intended use)name: Pentest Checklist
-
low Risky intent
intent-offensive-securitySKILL.md:3Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)description: This skill should be used when the user asks to "plan a penetration test", "create a security assessment checklist", "prepare for penetration testing", "define pentest scope", "follow sec
quoted -
low Risky intent
intent-offensive-securitySKILL.md:9Offensive-security / dual-use content (legitimate for authorised testing; review intended use)# Pentest Checklist
-
low Risky intent
intent-offensive-securitySKILL.md:25Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Defined pentest scope and objectives
-
low Risky intent
intent-offensive-securitySKILL.md:38Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- [ ] **Validate pentest necessity** - Ensure penetration test is the right solution
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens)
Process rating: all ten parameters 72/100
- 30Running it twice. 6 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 40Consistency. Frontmatter name (Pentest Checklist) differs from the folder (pentest-checklist)
- 50Failures and branches. 0 branches, has a failure section
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 107 steps
- 100Execution cost. Instruction body is 2453 tokens
- 100Progress reporting. Reports progress
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
- +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
- +5Description quotes 5 example trigger phrases
- +3Description length 288: enough signal without eating the budget
- +4Structure: 40 headings
- +3Step-by-step instructions: 107 items
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.