CtrlK
BlogDocsLog inGet started
Tessl Logo

verb-tampering

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

64

Quality

76%

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

The content is a lean, highly actionable security skill with copy-paste PoCs and a useful decision-gate workflow. Its main weakness is minor redundancy across the method-override and bypass-pattern sections, and a few implicit validation steps that could be made explicit.

Suggestions

Consolidate the method-override material so the mechanic appears once (section 3) and is only referenced from the bypass-patterns and chains tables to remove redundancy.

Make validation explicit in the PoC workflow (e.g. a numbered 'Confirm side-effect / verify state changed' checkpoint after each state-changing exploit) to push workflow clarity toward 5.

Consider moving the large bypass-pattern and chains tables into a reference file if the skill grows, keeping SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's knowledge of HTTP without padding, but there is minor redundancy — method-override mechanics recur in section 3, the bypass-patterns table, and the chains table — that could be tightened.

4 / 5

Actionability

Fully executable copy-paste curl one-liners throughout (verb sweep, HEAD bypass, override headers, Rails _method, Tomcat PUT webshell, OPTIONS leak, TRACE/XST) cover the common cases concretely.

5 / 5

Workflow Clarity

A clear detect → exploit → chain sequence exists with a decision-gate section providing checkpoints ('Confirm with a state-changing PoC, escalate') and side-effect confirmation, though some validation steps are implicit rather than spelled out.

4 / 5

Progressive Disclosure

Well-organized into nine clearly headed sections with one-level-deep cross-references to sibling skills and no nested references; no bundle files exist, and the single-file structure is appropriate, though some large tables/PoC blocks could conceptually be split out.

4 / 5

Total

17

/

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.

The description is specific and distinct, naming concrete attack vectors and natural trigger terms, but it omits an explicit 'Use when…' clause so it only answers 'what' and not 'when'. Adding a trigger-usage clause would raise completeness.

Suggestions

Append an explicit 'Use when…' clause listing trigger scenarios (e.g. 'Use when testing for method-based auth bypass, HEAD/OPTIONS bypass, or X-HTTP-Method-Override handling') to satisfy the completeness 'when' requirement.

Add a few more natural trigger synonyms to the description itself (e.g. 'BFLA via method', 'method-based authorization') that currently live only in metadata.when_to_use.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete vectors — 'auth bypass via HEAD/OPTIONS/arbitrary methods', 'X-HTTP-Method-Override', 'TRACE/PUT/DELETE exposure', 'framework routing flaws' — but these are attack categories rather than a fully comprehensive enumeration of actions.

4 / 5

Completeness

Has a clear 'what' (HTTP verb/method tampering and its bypass mechanisms) but no explicit 'Use when…' trigger clause, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Good natural keyword coverage including synonyms ('HTTP verb tampering', 'method tampering') and specific verbs (HEAD, OPTIONS, TRACE, PUT, DELETE, X-HTTP-Method-Override) a user would say, though a few common variants (e.g. 'BFLA', 'method-based authorization') are absent from the description.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (HTTP verb/method tampering) with distinct, specific triggers that are unlikely to fire for unrelated skills.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
PurpleAILAB/Decepticon
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.