CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

osint-recon

Gather and correlate open source intelligence from public sources for authorized investigations, threat intelligence, and attack surface assessment. Use when the user mentions 'OSINT,' 'open source intelligence,' 'digital footprint,' 'public records,' 'threat intelligence,' 'investigate a domain,' or needs to research a target using publicly available data.

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-organized, appropriately guarded single-file skill: concrete commands for infrastructure OSINT, a mandated authorization gate, a two-source validation rule, and a structured report template. The main gaps are the source-list-only sections that lack executable guidance and the implicit rather than explicit workflow sequencing.

Suggestions

Add one concrete, executable command or query example to the source-list sections — e.g., a HaveIBeenPwned API curl for email breach checks, a Google dork bundle for organization/document OSINT, or an exiftool batch invocation — so Organization, Email/Username, and Threat Intelligence sections match the actionability of the Domain/Infrastructure section.

Make the workflow sequence explicit: number the phases (1. Confirm authorization, 2. Collect per technique, 3. Analyze and cross-validate with two independent sources, 4. Produce the report in the output format) so the sequence does not rely on section ordering alone.

Trim redundant framing: the opening line under the title duplicates the frontmatter description, and generic source-name lists with no usage hint could be tightened or given a one-line 'use for X' purpose each so every token earns its place.

DimensionReasoningScore

Conciseness

The body is lean and list-driven with almost no explanation of concepts Claude already knows, but a few tokens could be trimmed — the opening sentence ('Systematically gather, analyze, and correlate publicly available information from open sources') restates the frontmatter description, and some source-name lists (Shodan, Censys, VirusTotal) add little beyond names. It is not 5 because not every token earns its place, and not 3 because the padding is minor.

4 / 5

Actionability

It gives copy-paste-ready commands for whois, dig, the crt.sh curl|jq pipeline, exiftool, and concrete Google dork syntaxes, plus a full markdown report template. However, the Organization, Email/Username, and Threat Intelligence sections are bare source lists with no executable how-to, which keeps it below the 'fully executable, covers common cases' anchor.

4 / 5

Workflow Clarity

The section ordering forms a clear sequence (Authorization check → Collection → Analysis → Output) and includes real validation checkpoints (four-point authorization checklist, 'validate information with at least two independent sources', confidence rating with defined High/Medium/Low levels). It is not 5 because the sequence is implied by section order rather than explicitly enumerated as steps with feedback loops.

4 / 5

Progressive Disclosure

As a single-file skill with no bundle files, everything lives in SKILL.md at an appropriate overview altitude with clear, navigable section headers and no nested references. It is not 5 because at ~120 lines with five collection subsections, per-technique detail (e.g., a source-by-source playbook) is at the boundary of what could be split into reference files, leaving minor organization headroom.

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 with explicit what/when structure, third-person voice, and rich natural trigger terms. Its main weakness is that the capability statement stays at the domain level ('gather and correlate') without naming the concrete techniques the skill actually covers.

DimensionReasoningScore

Specificity

The description names the domain and two concrete actions ('Gather and correlate open source intelligence from public sources') but does not enumerate specific sub-capabilities such as infrastructure mapping, breach exposure checks, or document metadata analysis, matching the '1-2 concrete actions, not comprehensive' anchor rather than the 'several specific actions' anchor.

3 / 5

Completeness

It explicitly answers both 'what' (gathering and correlating open source intelligence from public sources for authorized investigations, threat intelligence, and attack surface assessment) and 'when' (a concrete 'Use when the user mentions...' clause with specific trigger phrases), matching the top anchor exactly. It is not score 4 because the 'when' is already fully explicit with concrete triggers.

5 / 5

Trigger Term Quality

It provides comprehensive natural trigger coverage including the essential synonym pair ('OSINT', 'open source intelligence') plus 'digital footprint', 'public records', 'threat intelligence', 'investigate a domain', and a situational clause ('needs to research a target using publicly available data'); no common natural variation for this domain is missing.

5 / 5

Distinctiveness Conflict Risk

'OSINT' is a clear niche trigger, but 'investigate a domain' and 'threat intelligence' create minor overlap risk with closely related recon and threat-intel skills, fitting 'mostly distinct; minor overlap risk' rather than anchor 5's 'minimal conflict risk'.

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/osint-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.