CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

smuggling

HTTP Request Smuggling (HRS) — front-end / back-end parser disagreement attacks that desync the proxy stack. Covers CL.TE, TE.CL, TE.TE, CL.0, HTTP/2 downgrade (h2.cl, h2.te), pipelining, and connection-state pinning. Includes a confirm-desync gate, header obfuscation catalog, and minimal raw-socket Python harnesses (no smuggler.py available in sandbox).

Quality

79%

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

Quality

Content

70%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 deeply actionable, well-gated exploit workflow whose confirm-desync gate and validation discipline are exemplary. The main costs are token efficiency (the same anti-brute-force and timeout rules are repeated multiple times) and the total absence of progressive disclosure — a 650-line monolith where three or four chapters belong in separate reference files.

Suggestions

State the 'smuggling beats credential brute-force when tags co-occur' rule once (in When This Skill Is Primary) and reference it elsewhere in one line instead of restating the full reasoning in the Class A anti-pattern and 'Why this beats brute-force' sections.

Split the Class C chapter, the triple-tier desync matrix, and the PortSwigger lab pattern reference into references/ files (e.g. references/class-c-diagnostics.md, references/triple-tier.md, references/labs.md), keeping SKILL.md as a gate + variant-catalog overview.

Complete the fragmentary snippets (TE.CL, B1, B2) with the same send/receive loop used in the gate, or fold them into a single reusable harness function so every payload block is copy-paste executable.

DimensionReasoningScore

Conciseness

Mostly efficient — the harnesses, gates, and catalogs are operational content Claude does not already know — but noticeably padded in places: the 'brute-force is a fallback only after the confirm-desync gate fires NEGATIVE' rule is restated near-verbatim in three sections (When This Skill Is Primary, the Class A ANTI-PATTERN block, Why this beats brute-force), and timeout discipline is repeated across Variant Catalog, Anti-Patterns, and Class C. Fits the 'mostly efficient but could be tightened' anchor, not the verbose anchor since the majority of tokens are non-generic operational detail.

3 / 5

Actionability

The confirm-desync gate, Class A detection, and cookie-replay blocks are fully executable copy-paste Python/bash with timeouts and bounded recv loops, and the TE.TE obfuscation table gives exact header lines. Minor gaps: the TE.CL, B1, and B2 snippets are payload-construction fragments without send/receive code ('# Send + read 2 responses'), and B3 plus the sibling-resource enumeration loop are comment-only skeletons. 'Mostly executable guidance with minor gaps' — not 5 because several blocks require the reader to reassemble the surrounding harness.

4 / 5

Workflow Clarity

Excellent sequencing with explicit validation checkpoints and feedback loops: recognition signals → a mandatory confirm-desync gate with enumerated pass criteria and a fail-pivot ('do NOT iterate variants... Hand back to recon') → variant catalog → a Class A/B routing decision tree with run-FIRST detection probes → a verification section requiring 'Repro the smuggle three times' and explicit acceptable evidence. Stop rules and time-boxes ('each is a 5-minute time-box', 'if 8+ outer-pair variants... STOP') make error recovery unambiguous.

5 / 5

Progressive Disclosure

Section headers and navigation within the file are good, but there are no bundle files at all: ~650 lines are entirely inlined, and the Class C chapter, the triple-tier desync matrix, and the PortSwigger lab pattern reference are content that clearly belongs in references/ files. Fits 'some structure but content that should be separate is inline'; not 2 because the file is well-organized with clear headers rather than a headerless wall of text.

3 / 5

Total

15

/

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 highly specific, distinctive description with excellent trigger-term coverage of the smuggling variant vocabulary. Its only material weakness is the absence of an explicit 'Use when...' clause inside the description itself — trigger guidance is relegated to metadata.when_to_use, which caps completeness.

Suggestions

Append an explicit trigger clause to the description, e.g. 'Use when the user mentions request smuggling, HRS, desync, CL.TE/TE.CL mismatches, or multi-proxy/parser-disagreement behavior' — this converts the completeness score from 3 to 5 without adding real length.

Surface one or two of the strongest when_to_use phrases (e.g. 'request smuggling', 'desync') inside the description body so the field is self-sufficient for skill matching even if metadata is ignored.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities with comprehensive coverage: 'Covers CL.TE, TE.CL, TE.TE, CL.0, HTTP/2 downgrade (h2.cl, h2.te), pipelining, and connection-state pinning' plus 'confirm-desync gate, header obfuscation catalog, and minimal raw-socket Python harnesses'. No gaps in coverage and no vague language; third-person voice throughout.

5 / 5

Completeness

The 'what' is clear and comprehensive, but the description contains no 'Use when...' clause or equivalent explicit trigger guidance — the when-to-use terms live only in metadata.when_to_use, outside the description field. Per the rubric guideline this caps completeness at 3 (clear 'what', 'when' missing from the evaluated text).

3 / 5

Trigger Term Quality

Comprehensive natural-term coverage: 'HTTP Request Smuggling (HRS)' (full name + acronym), 'desync', 'parser disagreement', and every variant keyword a practitioner would actually say (CL.TE, TE.CL, TE.TE, h2.cl, h2.te, pipelining, connection-state pinning). Matches the comprehensive-synonyms anchor.

5 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers: variant names like 'CL.TE', 'h2.te', and 'desync' are unmistakable smuggling signals that no other skill would claim. Conflict risk with adjacent web-exploitation skills is minimal.

5 / 5

Total

18

/

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

skill_md_line_count

SKILL.md is long (657 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

Total

14

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

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