BC Pentest Commands
Essential penetration testing command reference. Quick lookup for nmap, Metasploit, hydra, john, nikto, gobuster, and other offensive security tools. Covers reconnaissance, exploitation, post-exploitation, and lateral movement.
Essential penetration testing command reference.
As a process C 61/100 · Has gaps — weak spots: result and completion, when it triggers, consistency
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-card.md:2Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Essential penetration testing command reference for quick lookup of nmap, Metasploit, hydra, john, nikto, gobuster, and other offensive security tools across reconnaissance, exploitation, post-exploit
-
low Risky intent
intent-offensive-securityskill-card.md:27Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- [ClawHub skill page](https://clawhub.ai/solomonneas/pentest-commands) <br>
-
low Risky intent
intent-offensive-securitySKILL.md:2Offensive-security / dual-use content (legitimate for authorised testing; review intended use)name: Pentest Commands
-
low Risky intent
intent-offensive-securitySKILL.md:4Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)description: "Essential penetration testing command reference. Quick lookup for nmap, Metasploit, hydra, john, nikto, gobuster, and other offensive security tools. Covers reconnaissance, exploitation,
quoted -
low Risky intent
intent-offensive-securitySKILL.md:10Offensive-security / dual-use content (legitimate for authorised testing; review intended use)# Pentest Commands
-
low Risky intent
intent-offensive-securitySKILL.md:14Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Provide a comprehensive command reference for penetration testing tools including network scanning, exploitation, password cracking, and web application testing. Enable quick command lookup during sec
-
low Risky intent
intent-offensive-securitySKILL.md:18Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Kali Linux or penetration testing distribution
Files scanned: 2. 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) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 61/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (Pentest Commands) differs from the folder (pentest-commands)
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 14 steps
- 100Execution cost. Instruction body is 2264 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 227: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 14 items
- +4Has examples (19 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.