BF web2-recon
Web2 recon pipeline — subdomain enumeration (subfinder, Chaos API, assetfinder), live host discovery (dnsx, httpx), URL crawling (katana, waybackurls, gau), directory fuzzing (ffuf), JS analysis (LinkFinder, SecretFinder), continuous monitoring (new subdomain alerts, JS change detection, GitHub commit watch). Use when starting recon on any web2 target or when asked about asset discovery, subdomain enum, or attack surface mapping.
Web2 recon pipeline — subdomain enumeration (subfinder, Chaos API, assetfinder), live host discovery (dnsx, httpx), URL crawling (katana, waybackurls, gau)…
As a process F 47/100 · Will not run — References files that are not bundled: id|user|file|path|url|redirect|next|src|token|key|api_key
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Dangerous commands
cmd-shell-rcSKILL.md:19Writes to a shell startup file (documentation of a security skill)echo 'export CHAOS_API_KEY="your-key-here"' >> ~/.zshrc
security skill -
low Dangerous commands
cmd-cron-mentionSKILL.md:311Mentions editing / listing crontab (documentation of a security skill)# Schedule: crontab -e → 0 8 * * * /bin/bash ~/monitors/subs-watch.sh
security skill
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5908 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: id|user|file|path|url|redirect|next|src|token|key|api_key - note
frontmatter-keyunknown frontmatter key "sources" - note
edit-residuethe text marks something as outdated (lines 584): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 47/100
- 0Tools and files. 1 referenced file(s) missing: id|user|file|path|url|redirect|next|src|token|key|api_key
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 5908 tokens
- 100Steps. 43 steps
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 17 top-level sections: this looks like several domains in one skill
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)
- +1No license
- +2Single-language instructions
- +3Description length 433: enough signal without eating the budget
- +4Structure: 46 headings
- +3Step-by-step instructions: 43 items
- +3Output format is stated explicitly
- +4Has examples (23 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.