CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

xxe

Hunt XML External Entity flaws in parsers and validate file read / SSRF impact with strict negative controls.

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/analyst/xxe/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 impressively lean playbook with concrete sink lists and, notably, an explicit validation section including negative controls — rare for this skill class. The main weakness is that the core payload step is described rather than given: no executable XML payloads (file-read or blind/OOB) and no remediation-check commands, so the reader must construct the actual test payloads themselves.

Suggestions

Add copy-paste-ready payload XML for each case (e.g., a DOCTYPE with a SYSTEM entity for file read, and a parameter-entity payload pointing to an attacker-controlled host for blind/OOB).

Include the concrete checks for "Dangerous defaults" — e.g., the specific Java feature flags (disallow-doctype-decl, external-general-entities) or Python/lxml parser config options to look for.

Add a short error-recovery path when the positive control fails (e.g., retry with parameter entities, OOB DNS/HTTP channels, or try alternate parsers in the same application).

DimensionReasoningScore

Conciseness

The ~20-line body is pure signal: named parser classes per language, a checklist of dangerous defaults, one-line payload targets, and a validation section. It assumes Claude's competence (no XML/DTD primer), and every line earns its place — squarely matching the lean-and-efficient anchor.

5 / 5

Actionability

Sink hunting is concrete (specific classes like `DocumentBuilderFactory`, `lxml.etree`), but the payload guidance is descriptive rather than executable — "entity to `file:///etc/passwd`" instead of a copy-paste XML payload with DOCTYPE/ENTITY declarations, and blind/OOB payloads are absent despite the frontmatter advertising them. This lands between "some concrete guidance but incomplete" (3) and "mostly executable" (4); the missing ready-to-use payload XML keeps it at 3.

3 / 5

Workflow Clarity

The section order (find sinks → check dangerous defaults → send payloads → validate) forms a clear, logical sequence, and a Validation section with explicit positive and negative controls is present, satisfying the rubric's requirement for verification in risky operations. It falls short of 5 because steps are implied by headers rather than sequenced, and there is no error-recovery guidance (e.g., what to try when the positive control fails, such as switching to blind/OOB exfiltration).

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, with no bundle files (references/, scripts/, assets/ are absent) and no external content that needs splitting. Per the rubric's simple-skill guideline, well-organized sections alone qualify for a 5 here.

5 / 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.

A tight, specific, third-person description that names a clear niche and several concrete actions with strong, natural trigger terms. Its main weakness is the absence of any explicit "Use when" trigger guidance inside the description itself, and the omission of the "XXE" acronym users most commonly type.

Suggestions

Add an explicit trigger clause, e.g. "Use when auditing XML parsing code, or when the user mentions XXE, DTDs, or external entities."

Include the acronym "XXE" in the description text, since it is the most common way users refer to this vulnerability class.

Consider mentioning blind/OOB detection to round out coverage of the technique families the skill addresses.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Hunt XML External Entity flaws in parsers", "validate file read / SSRF impact", "strict negative controls" — grounded in a specific domain (XML parsers). Minor gaps: it does not mention payload construction or blind/OOB detection, so it does not reach comprehensive coverage (5), but it clearly exceeds the 1-2 action level (3).

4 / 5

Completeness

The "what" is clear and concrete (hunt XXE flaws in parsers, validate file read/SSRF impact with negative controls), but the description contains no "Use when..." clause or equivalent trigger guidance; per the rubric guideline this caps completeness at 3 even though trigger keywords exist separately in metadata.when_to_use. It is not a 4 because the "when" is absent from the description rather than merely under-specified.

3 / 5

Trigger Term Quality

Natural terms a user would say are present: "XML External Entity", "file read", "SSRF", "parsers". A few common variations are missing from the description itself — notably the acronym "XXE" (the most common phrasing) and terms like "DTD" or "billion laughs" — placing it between good coverage (4) and comprehensive synonym coverage (5).

4 / 5

Distinctiveness Conflict Risk

"XML External Entity" combined with "file read / SSRF" defines a clear niche with distinct triggers and minimal overlap risk — no generic-skill conflict. Slight adjacency to broader SSRF/web-security skills, but the XXE framing is unambiguous.

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/analyst/xxe/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.