CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

api-soap-wsdl

SOAP / WSDL exploitation — WSDL enumeration via ?wsdl, XXE in SOAP envelope, WS-Addressing replay, WS-Security UsernameToken brute, SAML token injection in WS-Trust, schema validation bypass.

Quality

78%

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/api/soap-wsdl/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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 lean, concrete attack catalog with mostly copy-paste-ready payloads and good section organization. Its weaknesses are the absent validation/decision checkpoints (how to confirm a WSDL parsed, how to read SOAP fault responses, which attack to try first) and a few incomplete examples (the @ws-attack.xml payload file, the WS-Addressing fragment).

Suggestions

Add an explicit attack sequence with checkpoints, e.g. '1. Fetch and parse the WSDL, 2. List operations/parameters from the XSD types, 3. Pick an attack from the catalog, 4. Inspect the SOAP fault code/body to confirm or rule out each vulnerability'.

Provide the complete @ws-attack.xml UsernameToken payload inline (or as a bundle file) and a full WS-Addressing replay request instead of a one-line fragment.

Add brief response-interpretation guidance for each attack (what a successful XXE, UsernameToken hit, or schema-bypass response looks like versus a generic SOAP fault).

DimensionReasoningScore

Conciseness

The body is lean and assumes competence: a one-line context sentence, then immediately concrete commands and payloads with only functional comments (e.g. "# WSDL endpoints — try ?wsdl on any .asmx (.NET) / .svc (WCF) / Spring-WS endpoint"). No concepts are re-explained and every section earns its tokens.

5 / 5

Actionability

Mostly executable: the XXE curl with full SOAP envelope, Billion-Laughs payload, SOAPAction routing curl, and discovery commands are copy-paste ready. Minor gaps remain — "curl -sk -X POST -d @ws-attack.xml" references a payload file that is never provided, the WS-Addressing replay shows only a fragment instead of a full request, and the UsernameToken brute is a comment ("Brute: cycle a username dict, observe response time/error class") rather than a runnable command.

4 / 5

Workflow Clarity

The sequence is implicit (Discovery section first, then the attack catalog, then tooling/OPSEC) but there is no explicit ordering guidance, no validation checkpoints (e.g. confirm the WSDL parsed and identify the real operation names before attacking), and no feedback loop for interpreting SOAP faults versus successful injection. This matches 'sequence present but checkpoints missing or implicit'.

3 / 5

Progressive Disclosure

Well-organized single-file structure with clear sections (Discovery → attack catalog → Tooling → OPSEC → References) and a clearly signaled one-level-deep deferral to the SAML skill for XSW patterns. At ~110 inline lines it exceeds the 'under 50 lines' exception, and the tooling/catalog detail could plausibly live in a reference file, so it falls just short of the top anchor.

4 / 5

Total

16

/

20

Passed

Description

71%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, well-scoped description in third-person voice that names concrete attack techniques, but it omits any explicit 'when to use' trigger clause, leaving the completeness dimension capped. Trigger terms are strong but the description could surface the file extensions and framework keywords currently buried in metadata.when_to_use.

Suggestions

Append an explicit trigger clause to the description itself, e.g. 'Use when testing SOAP/WSDL endpoints (.asmx, .svc), WCF services, or WS-* security flows', rather than relying on metadata.when_to_use.

Fold the high-value trigger terms from metadata.when_to_use (.asmx, .svc, WCF, spring-ws) into the description so the description alone carries the trigger signal.

Consider scoping the SAML mention to WS-Trust contexts ('SAML token injection in WS-Trust') to further distinguish it from a dedicated SAML skill.

DimensionReasoningScore

Specificity

The description lists six concrete attack actions — "WSDL enumeration via ?wsdl, XXE in SOAP envelope, WS-Addressing replay, WS-Security UsernameToken brute, SAML token injection in WS-Trust, schema validation bypass" — giving comprehensive, specific coverage of the SOAP/WSDL exploitation domain rather than vague claims.

5 / 5

Completeness

The 'what' is clear and concrete, but the description contains no 'Use when...' clause or equivalent explicit trigger guidance — that information lives in metadata.when_to_use, not the description — which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Strong natural keywords (SOAP, WSDL, XXE, SAML, WS-Security) that a user testing these endpoints would actually say, but file extensions like .asmx/.svc and synonyms such as 'web service' appear only in metadata.when_to_use, not in the description itself, so a few natural terms are missing.

4 / 5

Distinctiveness Conflict Risk

SOAP/WSDL is a well-defined niche with distinct technical triggers, but "SAML token injection in WS-Trust" overlaps with a hypothetical dedicated SAML skill (the body itself defers XSW patterns to a separate SAML skill), creating minor overlap risk.

4 / 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/api/soap-wsdl/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.