CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

conducting-external-reconnaissance-with-osint

Conduct external recon using OSINT techniques to map an organization's external attack surface without touching target systems, gathering DNS records, certificate transparency logs, search results, social media, code repositories, and breach databases into a target profile. Use for the passive info-gathering phase of a pentest, external footprinting, or collecting employee/email intel for a social engineering campaign.

Quality

81%

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

63%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.

The content is a well-sequenced, largely executable recon workflow with a strong worked scenario and output template. Its main weaknesses are padded sections re-explaining concepts and tools Claude already knows, and a progressive-disclosure failure: the bundled `scripts/agent.py` and `references/api-reference.md` are never referenced from the body, leaving them orphaned.

Suggestions

Add a short 'Automation & References' section pointing to `scripts/agent.py` for automated collection (with its CLI usage) and `references/api-reference.md` for function-level and API details, so the bundle files are discoverable.

Remove or drastically trim the 'Key Concepts' table and 'Tools & Systems' section — Claude already knows what OSINT, certificate transparency, Shodan, and Amass are; keep only target-specific or non-obvious usage notes.

Insert explicit validation checkpoints between steps (e.g., 'resolve and dedupe all subdomains before Shodan/IP correlation; confirm API keys respond before relying on paid sources') to close the workflow's validation gaps.

DimensionReasoningScore

Conciseness

The workflow steps themselves are lean and command-driven, but the "Key Concepts" table (defining OSINT, passive/active reconnaissance, Certificate Transparency, Google Dorking, Shadow IT) and the "Tools & Systems" section explaining what Amass, Shodan, and theHarvester are re-teach concepts and tools Claude already knows. This matches the level-3 anchor 'Mostly efficient but includes some unnecessary explanation or could be tightened'; it is not severely padded (level 1-2) since the bulk of the body is dense, useful guidance.

3 / 5

Actionability

Most guidance is copy-paste ready: `amass enum -passive -d target.com -o amass_subs.txt`, the crt.sh curl|jq pipeline, `dig axfr @ns1.target.com target.com`, `shodan search "ssl.cert.subject.cn:target.com"`, and specific GitHub dorks. A few steps remain high-level hints ("Use `hunter.io` to determine the email format", "Review employee social media profiles"), matching level 4 'Mostly executable guidance; concrete code or commands with minor gaps' rather than the fully-executable coverage of level 5.

4 / 5

Workflow Clarity

The five-step workflow is clearly sequenced (DNS → infrastructure → personnel → leaks → tech stack) with a consolidation step and a concrete output-format template that serves as the end-state checklist, and the pitfalls warn against scope-creeping into active scanning. Validation checkpoints are implicit rather than explicit (e.g., no 'verify subdomains resolve before Shodan correlation'), which fits level 4 'Clear sequence with most checkpoints present; minor validation gaps' and falls short of level 5's explicit validate-fix-retry loops. This is passive recon, so the destructive/batch cap does not apply.

4 / 5

Progressive Disclosure

The body is well-sectioned (When to Use, Prerequisites, Workflow, Scenarios, Output Format), but it never references the bundle files that actually exist — `scripts/agent.py` and `references/api-reference.md` are orphaned and undiscoverable from SKILL.md, while tool/API detail that belongs in those files is inlined instead. This matches level 3 ('references present but not clearly signaled; content that should be separate is inline') — the internal structure prevents a score of 2, but the complete absence of navigation to real bundle files blocks level 4.

3 / 5

Total

14

/

20

Passed

Description

92%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: third-person voice, specific and comprehensive capability listing, and an explicit 'Use for' clause with natural pentest-phase trigger terms. The only minor gap is a few missing synonyms (e.g., 'subdomain enumeration', 'passive recon') that users might naturally say.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "map an organization's external attack surface", "gathering DNS records, certificate transparency logs, search results, social media, code repositories, and breach databases into a target profile" — giving comprehensive, specific coverage of what the skill does. It clearly matches the anchor 'Lists multiple specific concrete actions; comprehensive coverage' and exceeds the level-4 anchor, which expects minor gaps in coverage.

5 / 5

Completeness

It explicitly answers both questions: the "what" (passive recon gathering DNS, CT logs, social media, code repos, and breach data into a target profile) and an explicit "Use for..." clause naming the passive info-gathering phase of a pentest, external footprinting, and social engineering prep. This matches the level-5 anchor with concrete trigger phrases; level 4 would require the 'when' to be less explicit.

5 / 5

Trigger Term Quality

Natural trigger phrases include "external recon", "OSINT", "passive info-gathering phase of a pentest", "external footprinting", and "employee/email intel for a social engineering campaign" — terms a user would genuinely say. A few common variations are missing (e.g., "subdomain enumeration", "passive recon"), so it fits the level-4 anchor 'Good keyword coverage; a few natural terms missing' rather than the comprehensive synonym coverage of level 5.

4 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche — passive OSINT with the explicit boundary "without touching target systems" — which distinguishes it from active scanning or vulnerability-assessment skills. Triggers like "passive info-gathering phase" and "external footprinting" are unlikely to fire the wrong skill, matching the level-5 anchor 'Clear niche with distinct triggers; minimal conflict risk'.

5 / 5

Total

19

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

mukul975/Anthropic-Cybersecurity-Skills

Path

skills/conducting-external-reconnaissance-with-osint/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.