exploit-ssrf

Server-Side Request Forgery (SSRF) — exploiting server-side URL fetching to access internal services, cloud metadata (AWS/GCP/Azure), internal APIs, and port scanning. Covers IP bypass techniques, DNS rebinding, Gopher protocol smuggling, and redirect-based bypass.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/standard/exploit/web/ssrf/SKILL.md

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.

The body is a highly actionable, well-organized exploitation playbook with concrete executable commands and an explicit dead-end validation/pivot checkpoint. It is only mildly held back by a slightly long circuit-breaker narrative and the absence of any bundle-file offloading or linkified cross-references.

Suggestions

Convert the sibling-file references (ssti.md, exploit/PIVOT.md, SUMMARY.md) into markdown links so navigation is explicit and clickable.

Tighten the Circuit-Breaker narrative prose to its rule + numbered pivots, trimming the explanatory lead-in to improve token efficiency.

Consider splitting the large Gopher payload and full bypass-variant tables into a reference file to reduce inline weight and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean bash commands with brief comments and assumes Claude's familiarity with SSRF, but the opening sentence restates the description and the Circuit-Breaker narrative runs a little long, keeping it just below fully lean.	4 / 5
Actionability	Commands are fully executable and copy-paste ready across the common cases (AWS/GCP/Azure/DigitalOcean metadata, port and internal-host scanning, IP-encoding and redirect bypasses, a Gopher Redis payload, and file:// reads), matching the anchor.	5 / 5
Workflow Clarity	The mandatory Circuit-Breaker section provides an explicit 3-strike validation checkpoint with a feedback/pivot loop for the batch dead-end case, but the overall skill is organized as a technique catalog rather than a single linear sequence, so it sits just below the top anchor.	4 / 5
Progressive Disclosure	Content is well-sectioned with clear headers and appropriately delegates detail to sibling playbook files (ssti.md, exploit/PIVOT.md, recon SUMMARY.md); no bundle files exist, and minor gaps (cross-refs are not markdown links; everything is inline for a >50-line skill) keep it at 4.	4 / 5
	Total	17 / 20 Passed

Description

75%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.

The description is specific and distinctive, clearly communicating what the skill does and the techniques it covers. Its main weakness is the absence of an explicit 'Use when...' trigger clause inside the description field, leaving the 'when' guidance to the metadata.when_to_use list.

Suggestions

Add an explicit 'Use when...' clause to the description field naming concrete trigger phrases (e.g. 'Use when the user mentions SSRF, server-side URL fetching, cloud metadata endpoints, or 169.254.169.254') so the 'when' guidance lives in the evaluated field.

Fold a couple of the most natural synonyms currently only in metadata.when_to_use (such as '169.254.169.254' and 'IMDS') into the description to round out trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('access internal services, cloud metadata (AWS/GCP/Azure), internal APIs, and port scanning') plus concrete bypass techniques ('IP bypass', 'DNS rebinding', 'Gopher protocol smuggling', 'redirect-based bypass'), matching the comprehensive-coverage anchor.	5 / 5
Completeness	The 'what' is clearly stated, but there is no explicit 'Use when...' trigger clause in the description (trigger guidance is in metadata.when_to_use), so per the rubric guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	Good natural-term coverage including 'Server-Side Request Forgery (SSRF)', 'cloud metadata', 'port scanning', and 'Gopher', but a few natural synonyms (e.g. '169.254.169.254', 'IMDS') live only in the metadata.when_to_use field rather than the description itself.	4 / 5
Distinctiveness Conflict Risk	A clearly distinct niche (SSRF exploitation) with specific triggers that would not fire for unrelated skills, matching the minimal-conflict anchor.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: PurpleAILAB/Decepticon
Path: packages/decepticon/decepticon/skills/standard/exploit/web/ssrf/SKILL.md
Commit: 0cf691e

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.