CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ssrf

Hunt Server-Side Request Forgery (CWE-918) through taint analysis from user-controlled URLs to HTTP client sinks. Covers cloud metadata pivoting, DNS rebinding, gopher smuggling, and the IMDSv1 → IAM role chain that turns SSRF into RCE.

Quality

82%

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

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, practitioner-grade playbook: concrete commands, a validating PoC template with a negative control, and a clear audit-to-promotion workflow. The gaps are small — an unneeded motivational intro, incomplete tool-call signatures, no failure-path guidance, and no offloading of tabular material to reference files.

DimensionReasoningScore

Conciseness

The body is dense and operational (sink tables, grep patterns, bypass checklists, CVSS vectors) with little re-explanation of known concepts. The 5-line intro justifying why SSRF is 'one of the highest-yield vuln classes' is persuasion Claude does not need and could be trimmed.

4 / 5

Actionability

Concrete semgrep/grep commands, a copy-paste curl PoC, regex success patterns, and a negative control make most guidance executable. Minor gaps: 'kg_add_node(kind="vulnerability", ...)' and 'plan_attack_chains' invocations use ellipsis placeholders without full signatures.

4 / 5

Workflow Clarity

Section 4 gives a clear sequence (enumerate → trace data flow with concrete decision questions → record vulnerability → link code location) and section 5 adds explicit validation via success patterns plus a negative control. No error-recovery guidance exists for when validate_finding fails, keeping it below a 5; the PoCs are non-destructive so the batch/destruction cap does not apply.

4 / 5

Progressive Disclosure

Well-organized numbered sections with everything easy to navigate, but the ~100-line body is fully inline with no reference files; the sink-impact and CVSS tables are compact enough inline, yet the skill exceeds the under-50-line self-contained ideal, leaving minor organization headroom.

4 / 5

Total

16

/

20

Passed

Description

82%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, highly specific description with excellent trigger keywords and near-zero conflict risk. Its only weakness is the missing 'Use when...' clause: trigger guidance is split into a metadata.when_to_use field instead of the description, which weakens discovery when the description alone is consulted.

Suggestions

Add an explicit 'Use when...' sentence to the description (e.g., 'Use when auditing code or triaging findings for SSRF, CWE-918, cloud metadata exposure, or URL-fetch parameters') rather than relying on the separate metadata.when_to_use field.

Fold one or two natural trigger phrases from metadata.when_to_use (such as 'server side request forgery', 'ssrf', 'url fetch parameter') into the description body so the description is self-sufficient for routing.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'taint analysis from user-controlled URLs to HTTP client sinks', 'cloud metadata pivoting, DNS rebinding, gopher smuggling', and the 'IMDSv1 → IAM role chain' — giving comprehensive coverage of the SSRF hunting domain.

5 / 5

Completeness

The 'what' is clear (hunt SSRF via taint analysis to HTTP client sinks) but there is no 'Use when...' clause or equivalent trigger guidance in the description itself — triggers are relegated to a separate metadata.when_to_use field — which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes the full name ('Server-Side Request Forgery'), the abbreviation-domain idiom via CWE-918, and natural technique keywords ('cloud metadata', 'DNS rebinding', 'IAM role') that a security reviewer would actually say, with synonyms covered.

5 / 5

Distinctiveness Conflict Risk

Highly distinctive identifiers ('CWE-918', 'gopher smuggling', 'IMDSv1 → IAM role chain') give it a clear niche with minimal overlap risk, even against adjacent web-exploitation skills.

5 / 5

Total

18

/

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/analyst/ssrf/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.