CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

domain-intel

Passive recon of subdomains, SSL certs, WHOIS, and DNS.

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/research/domain-intel/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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, highly actionable overview whose heavy implementation is properly delegated to a real bundled script with copy-paste-ready command examples for all operations. Weaknesses are duplicated content across sections (firewall notes, tool-comparison bullets vs table) and missing error-handling/validation guidance for the batch bulk command.

Suggestions

Deduplicate: state the WHOIS TCP-43 firewall caveat once, and merge the "When to use this vs built-in tools" bullet list into the table (or vice versa).

Add brief error-recovery guidance for bulk runs: what to do when a check fails (e.g., port 43 blocked, crt.sh timeout), whether to retry, and how to interpret partial results.

Add one short example of the JSON output shape so users of the skill know what to parse without running a command first.

DimensionReasoningScore

Conciseness

The body is mostly efficient with executable commands and no explanation of concepts Claude already knows, but it is duplicated in places: the WHOIS TCP-43 firewall note appears in both "Platform compatibility" and "Notes", and the "When to use this vs built-in tools" bullet list repeats roughly half of the adjacent table's rows. This matches the 3 anchor (some unnecessary content, could be tightened) rather than 4, where only minor trimming would be needed.

3 / 5

Actionability

Every one of the six commands is shown as a copy-paste-ready invocation with a realistic domain, inline comments explaining each, an advanced flag example ("bulk example.com github.com --checks ssl,dns"), and an explicit definition of the SKILL_DIR placeholder — fully executable guidance covering the common cases.

5 / 5

Workflow Clarity

Each task is an unambiguous single command, but the "bulk" command is a batch operation and the skill provides no validation or error-recovery guidance for it (how to handle partial failures, crt.sh slowness, or blocked port 43 beyond noting it may happen). The rubric's batch-operation cap limits workflow clarity to 3 despite the single-command clarity.

3 / 5

Progressive Disclosure

The ~400-line implementation is correctly pushed into the verified scripts/domain_intel.py, with SKILL.md acting as a well-sectioned, one-level-deep overview (commands table, routing guidance, platform notes). It falls short of 5 because there is no references/ organization for the routing/comparison material and some inline content (the duplicated tool-comparison table) could live separately or be consolidated.

4 / 5

Total

15

/

20

Passed

Description

70%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 concise, third-person description that names a distinct passive-domain-OSINT niche with four concrete data areas and natural trigger keywords. Its main weakness is the complete absence of a "Use when..." trigger clause, which caps completeness at 3 and leaves "when to use" guidance only in the body.

Suggestions

Add an explicit trigger clause, e.g. "Use when asked about subdomains, SSL certificate expiry, domain registration/WHOIS, DNS records, or whether a domain is available."

Mention the domain-availability capability in the description since it is one of the script's six commands but is absent from the description.

Include a synonym or two for certificate work (e.g. "certificate expiry/inspection") to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

"Passive recon of subdomains, SSL certs, WHOIS, and DNS" names the domain and enumerates four concrete capability areas (subdomain discovery, certificate inspection, WHOIS, DNS), which is stronger than the 3 anchor's "1-2 concrete actions" but applies only one generic verb ("recon") rather than the distinct per-area actions a 5 would list, and omits the availability check.

4 / 5

Completeness

The description clearly answers "what" (passive recon of four enumerated targets) but contains no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3. It is above 2 because the "what" is concrete and multi-part.

3 / 5

Trigger Term Quality

"subdomains", "SSL certs", "WHOIS", and "DNS" are terms users naturally say when needing this skill, giving good keyword coverage. It falls short of the 5 anchor because common variations like "certificate expiry", "domain registration", "domain availability", or file extensions are absent.

4 / 5

Distinctiveness Conflict Risk

"Passive recon of subdomains, SSL certs, WHOIS, and DNS" carves out a clear niche (passive domain OSINT) with distinct triggers that a web-search or general-research skill would not claim, matching the 5 anchor's clear-niche/minimal-conflict profile.

5 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository

NousResearch/hermes-agent

Path

optional-skills/research/domain-intel/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.