CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

verb-tampering

HTTP verb/method tampering — auth bypass via HEAD/OPTIONS/arbitrary methods, X-HTTP-Method-Override, TRACE/PUT/DELETE exposure, framework routing flaws.

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

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

An excellent, dense, execution-ready reference: every section carries concrete commands or mechanics Claude would not reliably recall, with a validated detection workflow and a decision gate for escalation. Its only soft spots are mild redundancy around the method-override mechanic and a monolithic single-file layout that could split defender/tooling material into references.

DimensionReasoningScore

Conciseness

Largely lean and table-driven with payload-specific details Claude would not know (CVE numbers, .htaccess Limit semantics, trailing-slash Tomcat trick). Minor over-explanation exists — the method-override mechanic is stated in the intro, §1, and the §4 table, and XST appears in both §4 and §6 — so it is not the fully lean 5.

4 / 5

Actionability

Fully executable throughout: copy-paste curl verb sweeps with status-code interpretation, override-header loops, Rails _method body examples, a Tomcat PUT webshell PoC, and concrete tool invocations (nuclei template paths, nikto -Tuning 6, httpx -methods, ffuf -X). Placeholders (<TARGET>, $LOWPRIV_JWT) are the only substitution needed.

5 / 5

Workflow Clarity

Clear sequence — baseline-validated verb sweep in §2 ('If GET=401 but HEAD/OPTIONS=200 → candidate'), override tests in §3, PoCs with explicit side-effect confirmation in §5.1, and a §9 decision gate with failure paths ('Only response-size difference, no auth bypass → Low — fold into recon'). These constitute explicit validation steps, feedback loops, and a checklist, matching the top anchor; the batch verb sweep has validation so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

A single, well-sectioned file with clear numbered headers and one-level cross-references to sibling skills (BFLA, mass-assignment, HPP, WAF bypass, file-upload); no bundle files exist to mis-navigate. It misses a 5 because at ~170 lines it exceeds the simple-skill threshold and sections like defender signatures (§8) and the tools list (§7) could plausibly live in separate reference files.

4 / 5

Total

18

/

20

Passed

Description

70%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, distinctive description with strong trigger terminology for the verb-tampering niche. Its main weakness is the missing explicit 'Use when...' trigger clause in the description itself, which caps completeness and slightly narrows discoverability.

Suggestions

Append an explicit trigger clause to the description, e.g. 'Use when testing auth bypass via HTTP methods, verb tampering, HEAD/OPTIONS bypass, or X-HTTP-Method-Override.'

Add natural synonyms users would say — 'method override', 'HEAD bypass', 'OPTIONS', 'BFLA' — to broaden keyword coverage (several already exist in metadata.when_to_use but not in the description).

Convert topic nouns into capability verbs ('detect and exploit verb-based auth bypass...') to sharpen the 'what' without adding length.

DimensionReasoningScore

Specificity

The description lists several concrete capability areas — 'auth bypass via HEAD/OPTIONS/arbitrary methods, X-HTTP-Method-Override, TRACE/PUT/DELETE exposure, framework routing flaws' — each naming specific techniques. It stops short of a 5 because it names topics rather than actions (no 'detects/exploits' verbs) and omits coverage areas present in the body such as verb sweeps and WebDAV chaining.

4 / 5

Completeness

The 'what' is clear (verb-tampering-based auth bypass via specific methods and headers), but the description field contains no 'Use when...' trigger clause or equivalent, so completeness is capped at 3 per the judging guidelines. It is not a 2 because the 'what' is specific, not vague.

3 / 5

Trigger Term Quality

Good natural keywords users would say: 'HTTP verb/method tampering', 'auth bypass', 'X-HTTP-Method-Override', 'TRACE/PUT/DELETE'. A few natural terms are missing — 'method override', 'HEAD bypass', 'OPTIONS', 'BFLA' — preventing the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — HTTP verb/method tampering — with highly distinct triggers (X-HTTP-Method-Override, HEAD/OPTIONS/arbitrary verbs) that would not naturally fire for a generic auth-bypass or scanning skill. Minimal conflict risk.

5 / 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/exploit/web/verb-tampering/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.