CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

web-recon

Web application enumeration hub — directory/file fuzzing, vhost discovery, API enumeration, CMS scanning, WAF detection, auth surface mapping, cookie audit.

Quality

80%

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/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 lean, action-oriented hub that delegates detail to sub-skills and contributes real, non-inferable operational rules (dedup, resume, stop). Its few gaps are cosmetic: inconsistent reference formats in the fast-path table and a couple of vague first-action pointers.

DimensionReasoningScore

Conciseness

The body is lean and operational — two compact tables, one copy-paste bash snippet, terse resume/stop rules, and a file manifest — with zero explanation of concepts Claude already knows. The environment-specific knowledge it adds (resume-after-context-summarization via recon/probed.txt, the 5-probe pivot rule) is exactly what Claude could not infer, so every token earns its place.

5 / 5

Actionability

Mostly executable: exact load_skill paths, concrete SSTI payload ({{7*7}}), a working dedup/resume bash pattern, and named output files. It falls short of anchor 5 because some first actions are non-executable pointers — "Fire a single error-triggering payload" names no payload, and fast paths point to a "recon section" of other skills without a concrete step.

4 / 5

Workflow Clarity

A clear sequence is present (check tags → load matching sub-skill → deduplicated probe loop) with genuine checkpoints for the batch enumeration (grep-before-probe, tail -1 resume rule, 5-consecutive-same-response stop rule), so the batch-operation cap at 3 does not apply. It stops short of 5 because the workflow is assembled across sections rather than ordered, and there is no verification step for findings before handoff.

4 / 5

Progressive Disclosure

The hub pattern is well executed: one-level-deep references in a table with a "When to load" column, and no bundle files exist to inline. Minor organization gaps keep it at anchor 4 — the fast-path table inconsistently cites bare filenames ("discovery.md", "api-enumeration.md", "auth-mapping.md") while the main table uses full .../SKILL.md paths, making navigation slightly ambiguous.

4 / 5

Total

17

/

20

Passed

Description

71%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 highly specific, well-scoped description that clearly names the capability set, undermined by the complete absence of a "Use when..." trigger clause and by missing common synonyms (recon, reconnaissance, fingerprinting) that live only in metadata. Adding explicit trigger guidance would move it from good to excellent.

Suggestions

Append a trigger clause to the description, e.g.: "Use when the user asks for web recon, web application enumeration, directory/file fuzzing, or fingerprinting a web app" — this addresses the completeness cap of 3.

Fold natural synonyms currently stranded in metadata.when_to_use ("web recon", "reconnaissance", "web app fingerprint") into the description itself to lift trigger_term_quality toward 5.

Optionally note the output artifact (a consolidated web findings summary) in the description to further differentiate from sibling recon skills.

DimensionReasoningScore

Specificity

The description lists seven concrete, distinct capabilities ("directory/file fuzzing, vhost discovery, API enumeration, CMS scanning, WAF detection, auth surface mapping, cookie audit") with no vague filler, matching the anchor for multiple specific concrete actions with comprehensive coverage of the web-recon domain. It is written in third-person noun-phrase voice, so no person-voice penalty applies.

5 / 5

Completeness

The "what" is clear and concrete, but the description contains no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 4 because the "when" is absent entirely rather than merely under-specified.

3 / 5

Trigger Term Quality

Domain-natural terms like "enumeration", "fuzzing", "vhost discovery", and "WAF detection" are present and would be said by users requesting this work, but common synonyms users actually use — "web recon", "reconnaissance", "web app fingerprinting" — appear only in metadata.when_to_use, not in the description itself. This fits anchor 4 (good keyword coverage, a few natural terms missing) rather than 5 (comprehensive coverage including synonyms).

4 / 5

Distinctiveness Conflict Risk

"Web application enumeration hub" plus niche markers like vhost discovery, WAF detection, and cookie audit gives a clear niche with distinct triggers, but generic phrasings like "CMS scanning" leave minor overlap risk with sibling recon/exploit skills. Anchor 4 (mostly distinct; minor overlap risk) is the best fit.

4 / 5

Total

16

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

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