CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

xpath-xslt

XPath + XSLT injection — query manipulation in XML data stores, server-side XSLT RCE via document() / EXSLT extensions.

Quality

74%

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/xpath-xslt/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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, highly actionable injection payload reference whose code and PoCs are near copy-paste ready. Its weaknesses are a merely implicit detect-then-exploit workflow with no verification checkpoints, and a couple of incomplete or mislabeled payload examples.

Suggestions

Add an explicit detection-to-exploitation sequence with verification steps, e.g., confirm the injected XPath predicate changed the response, then verify document() output before escalating to EXSLT RCE, with fallback engines to try when extensions are disabled.

Complete the blind-extraction section: give a concrete boolean-extraction loop example and name which implementations support timing or out-of-band channels, instead of the current one-line comment.

Fix the EXSLT example attribution (the rt:exec runtime extension is Xalan-Java, not libxslt) and label each RCE payload with the engine and version it applies to so payloads are not fired against the wrong target.

DimensionReasoningScore

Conciseness

The body is a dense, payload-first reference with almost no padding; every section delivers attack-relevant material. It is not 5 because a few orientation lines explain concepts Claude already knows ('XPath = XML query language', the SQL-injection analogy), which could be trimmed.

4 / 5

Actionability

Most guidance is copy-paste ready: concrete injection payloads (' or '1'='1), a complete executable curl PoC with a full stylesheet for document() file read, and specific EXSLT RCE payloads. Minor gaps keep it below 5 — the time-based blind XPath technique is only a comment ('XPath has no sleep, but some impls support extensions'), and the EXSLT example mislabels a Xalan-Java extension as 'libxslt w/ Xalan-Java extension'.

4 / 5

Workflow Clarity

Sections (Detection, PoC, Severity, Defender) imply a loose detect-then-exploit flow, but there is no explicit sequence and no validation checkpoints — e.g., confirming document() actually returned content, or falling back to alternate engines when EXSLT is unavailable. The simple-skill exception does not apply (82 lines, multiple attack classes), and the implicit-only sequence matches anchor 3 rather than the explicit-checkpoint anchors 4-5.

3 / 5

Progressive Disclosure

A single self-contained file with clean section headers, appropriate for a compact payload cheat-sheet, plus a cross-references section pointing one level out (upstream corpus, XXE skill) rather than nesting. It does not reach 5 because the body exceeds the under-50-lines threshold where inline-only structure is automatically ideal — engine-specific EXSLT payload tables or blind-extraction technique detail could live in a reference file.

4 / 5

Total

15

/

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 that clearly conveys the attack classes covered, weakened only by the absence of an explicit 'Use when...' trigger clause and slightly incomplete capability enumeration. Adding a trigger clause and one or two capability keywords (auth bypass, file read) would lift it to the top anchors.

Suggestions

Append an explicit trigger clause, e.g. 'Use when testing XML-backed endpoints, login forms querying XML data stores, or endpoints applying XSLT transforms to user-controlled XML.'

Enumerate the main capabilities in the description — auth bypass, blind data extraction, file read/SSRF via document(), and EXSLT RCE — so the 'what' is comprehensive.

Include natural keyword variations users may say, such as 'XPath injection', 'XSLT injection', and 'XML query injection', to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description names several concrete capabilities — 'query manipulation in XML data stores', 'server-side XSLT RCE via document() / EXSLT extensions' — matching the anchor for several specific actions with minor gaps. It falls short of 5 because it omits key capabilities the body covers (auth bypass, file read, blind extraction) and is not comprehensive.

4 / 5

Completeness

The 'what' is clear (XPath query manipulation and XSLT RCE via document()/EXSLT), but there is no 'Use when...' clause or equivalent explicit trigger guidance; the 'when' is only weakly implied by the domain naming, which caps completeness at 3 per the judging guidelines. It is not 2 because the 'what' is concrete and specific rather than vague.

3 / 5

Trigger Term Quality

Natural trigger terms are present and specific to the niche ('XPath', 'XSLT', 'injection', 'document()', 'EXSLT'), giving good keyword coverage. It misses common variations a user might say ('XML injection', 'blind XPath', 'XPath injection'), so it does not reach the comprehensive-synonyms anchor 5.

4 / 5

Distinctiveness Conflict Risk

XPath/XSLT injection is a clear niche with distinct trigger terms; virtually no other skill would compete for these queries. The only adjacent skill (XXE) is a different XML attack class and is explicitly disambiguated in the body's cross-references, so conflict risk is minimal — matching anchor 5 rather than the minor-overlap anchor 4.

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/xpath-xslt/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.