CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

recon

Perform structured reconnaissance and attack surface enumeration for authorized penetration tests, CTF challenges, and bug bounty programs. Use when the user mentions 'recon,' 'reconnaissance,' 'enumerate,' 'attack surface,' 'subdomain enumeration,' 'port scan,' 'fingerprint,' 'asset discovery,' or needs to map a target's external footprint.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, security-conscious skill body: phases are clearly gated by authorization, most of the core workflow is command-driven, and boundaries are explicit. The main gaps are a handful of high-level sections without concrete commands (service enumeration, fingerprinting, code-repo searching) and the absence of validation/feedback checkpoints after active steps.

Suggestions

Add concrete commands or named tools to the vague sections — service enumeration (e.g., an nmap NSE or version-probe example), technology fingerprinting (e.g., a Wappalyzer/whatweb invocation), and GitHub/GitLab dorking (e.g., specific search query patterns) — to lift actionability from mostly-executable to fully executable.

Insert validation checkpoints in the workflow: re-confirm scope immediately before Phase 2, and a step to verify/handle failed or filtered scan results before enumerating services, which would also strengthen the feedback-loop quality of workflow_clarity.

Tighten small filler phrases (e.g., "Gather information without touching the target directly", "Correlate all findings.") that add tokens without adding instruction, nudging conciseness toward the lean anchor.

DimensionReasoningScore

Conciseness

The body is efficient — commands are given directly (dig, whois, nmap, crt.sh pipeline) with no tutorials on what these tools are and no concept explanations Claude already knows. Minor instances could be trimmed (e.g., "Gather information without touching the target directly", "Correlate all findings"), placing it just below the lean-and-efficient anchor 5 and well above anchor 3's unnecessary-explanation threshold.

4 / 5

Actionability

Most guidance is executable: `dig any $ARGUMENTS`, `dig axfr @ns-server $ARGUMENTS`, the crt.sh curl|jq pipeline, `whois $ARGUMENTS`, `nmap -sC -sV -oN scan-results.txt $ARGUMENTS`, named tools (gobuster/feroxbuster/dirsearch, testssl.sh/sslyze), and concrete API paths (/api/, /v1/, /graphql, /swagger.json). Gaps remain in service enumeration ("probe for version info and default configurations"), technology fingerprinting, and GitHub/GitLab searching, which stay high-level — mostly executable with minor gaps rather than the incomplete-guidance anchor 3.

4 / 5

Workflow Clarity

A clear three-phase sequence (Passive → Active → Analysis) with an explicit authorization gate before any commands ("Before running any commands, confirm: 1... 2..."), an explicit-authorization marker gating Phase 2, prioritization criteria, and a structured output template. It falls short of anchor 5 because there are no post-scan validation/feedback loops (e.g., re-verify scope before active steps, handle failed or filtered scans), but checkpoints are explicit rather than implicit, ruling out anchor 3.

4 / 5

Progressive Disclosure

No bundle files exist and the ~107-line body is well organized into clearly headed sections, with sibling-skill cross-references clearly signaled and a References section pointing to external standards (PTES, OWASP, jhaddix/tbhm) rather than nested files. Good structure with minor organization gaps — the methodology detail could arguably live in a reference file — so anchor 4 rather than the simple-skill anchor 5.

4 / 5

Total

16

/

20

Passed

Description

86%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: explicit what-and-when structure, third-person voice, and an unusually thorough set of natural trigger terms including synonyms. The only weakness is that the capability statement uses two umbrella actions rather than enumerating several concrete techniques, which slightly limits specificity.

DimensionReasoningScore

Specificity

The description names the domain plus two umbrella actions — "Perform structured reconnaissance and attack surface enumeration for authorized penetration tests, CTF challenges, and bug bounty programs" — but does not list several discrete concrete capabilities. It matches the anchor for naming the domain with 1-2 concrete actions rather than the several-specific-actions anchors (4/5) or the minimal-actions anchor (2).

3 / 5

Completeness

It explicitly answers both what ("Perform structured reconnaissance and attack surface enumeration for authorized penetration tests, CTF challenges, and bug bounty programs") and when, with a concrete 'Use when...' clause enumerating trigger phrases. This matches the anchor-5 example pattern exactly; a 4 would require a less explicit 'when'.

5 / 5

Trigger Term Quality

"Use when the user mentions 'recon,' 'reconnaissance,' 'enumerate,' 'attack surface,' 'subdomain enumeration,' 'port scan,' 'fingerprint,' 'asset discovery,' or needs to map a target's external footprint" gives comprehensive natural-term coverage including the recon/reconnaissance synonym pair and technique-level phrases users would actually say. Not 4 because no common variation is conspicuously missing.

5 / 5

Distinctiveness Conflict Risk

Triggers like 'port scan,' 'subdomain enumeration,' and 'attack surface' carve a distinct recon niche with minimal conflict risk, but the skill family includes closely related siblings (osint-recon, web-pentest per the body cross-references), leaving minor overlap risk — anchor 4 rather than the clear-niche anchor 5.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

briiirussell/cybersecurity-skills

Path

skills/recon/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.