CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

web-discovery

Web app discovery — directory/file fuzzing, vhost discovery, JavaScript endpoint extraction.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/standard/recon/web-recon/discovery/SKILL.md
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 tight, highly executable recon playbook: nearly copy-paste commands, sensible filters, and a rare explicit validation loop in the alias-probe section. Weaknesses are minor — a few trimmable concept explanations, occasional placeholders in place of executable steps, and no verification checkpoints outside the alias probe.

DimensionReasoningScore

Conciseness

The body is lean and command-dominant with skill-specific prose (alias misconfig rationale, anti-pattern callout), but small sections restate knowledge Claude already has — e.g., "Multiple applications may share one IP but respond differently based on Host header" — so it fits anchor 4 (minor over-explanation that could be trimmed) rather than 5, and is well above anchor 3's 'some unnecessary explanation'.

4 / 5

Actionability

Nearly all guidance is concrete, executable ffuf/curl/bash with real wordlist paths and complete loop constructs, matching anchor 4 (mostly executable, minor gaps). Not 5 because of placeholders requiring operator judgment ("-fs <default_size>") and a commented-out rather than executable confirmation step for alias candidates; well above anchor 3's pseudocode/incomplete level.

4 / 5

Workflow Clarity

Four clearly numbered, parallel recon phases with the alias probe containing genuine validation checkpoints — homepage baseline sizing, a flag condition ("Only flag if 200 AND size differs from homepage"), and a control-file confirmation step — fitting anchor 4. Not 5 because the other three sections lack any verification/feedback checkpoints and the phases are parallel rather than an explicit ordered sequence.

4 / 5

Progressive Disclosure

A single-file bundle with well-organized numbered sections, each technique placed appropriately, and nothing inlined that belongs in a separate reference file; the only external pointer ("see lfi.md") is a one-line sibling-skill cross-reference. This matches anchor 4; not 5 because at ~105 lines it exceeds the under-50-line simple-skill exception and a couple of probe recipes could live in reference files.

4 / 5

Total

16

/

20

Passed

Description

66%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 specific, well-scoped description that clearly communicates what the skill does through three concrete capabilities. Its main weakness is the absence of any explicit "Use when..." trigger guidance, which both caps completeness and slightly limits discoverability.

Suggestions

Add a "Use when..." clause naming natural trigger situations, e.g., "Use when enumerating hidden directories/paths, brute-forcing web content, discovering virtual hosts via Host header, or extracting API endpoints and secrets from JavaScript files."

Include common synonyms and file extensions users actually say — "content discovery", "directory brute force", "hidden paths", "source maps", ".js" — to strengthen trigger-term coverage.

DimensionReasoningScore

Specificity

Names three concrete actions — "directory/file fuzzing", "vhost discovery", "JavaScript endpoint extraction" — matching anchor 4 (several specific actions, minor gaps in coverage). Not 5 because sensitive-file checks and source-map detection from the body are not reflected.

4 / 5

Completeness

The "what" is clear (web app discovery covering directory fuzzing, vhost discovery, JS endpoint extraction) but there is no "Use when..." clause or equivalent explicit trigger guidance in the description field, capping completeness at anchor 3. It is not 4 because 'when' is entirely absent rather than merely imprecise; not 2 because the 'what' half is fully present and specific.

3 / 5

Trigger Term Quality

Includes good natural keywords ("directory", "fuzzing", "vhost", "JavaScript", "endpoint extraction") a user would plausibly say, but misses common variations like "content discovery", "brute force directories", "hidden paths/directories", and ".js". Matches anchor 4; a few natural terms missing, so not 5.

4 / 5

Distinctiveness Conflict Risk

The description carves out a distinct web-recon niche (directory fuzzing, vhosts, JS endpoint extraction) with little generic overlap, fitting anchor 4. Not 5 because "web app discovery" as a frame could mildly overlap with sibling recon skills such as subdomain enumeration or port scanning.

4 / 5

Total

15

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

packages/decepticon/decepticon/skills/standard/recon/web-recon/discovery/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.