CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

saml

SAML 2.0 attacks — XSW (XML Signature Wrapping) variants 1-8, comment injection, signature stripping, assertion forgery, IdP metadata abuse.

Quality

75%

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

Quality

Content

71%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 dense, practical attack playbook with real commands, payloads, tools, a decision-driven PoC workflow, and a useful severity table. Its weaknesses are a missing when-to-use framing in the description side, minor conceptual padding, schematic XML examples, and a monolithic single-file layout with cross-references to paths that don't exist in the bundle.

Suggestions

Split detail-heavy material (full XSW1-8 mechanics, known exemplars/CVEs, severity calibration) into references/ files inside the bundle and replace the dangling `skills/_corpus/...` cross-references with links to those real files.

Add the missing execution glue: a command or snippet for re-encoding a modified SAMLResponse (base64 + deflate) and re-submitting it, making the PoC pattern fully end-to-end.

Trim the opening background paragraph and the explanatory prose in sections 5-8 down to one-line statements of the attack condition, letting the XML examples carry the explanation.

DimensionReasoningScore

Conciseness

The body is largely lean — terse sections, XML payload snippets, and a severity table with no library surveys or padding. Minor over-explanation keeps it from a 5: the opening conceptual framing ("SAML is XML-based SSO used heavily in enterprise. Signatures protect assertions but XML's structural flexibility...") and explanatory prose in sections 5-8 restate things Claude already knows and could be trimmed to one line.

4 / 5

Actionability

Concrete, executable guidance dominates: `echo "$SAMLResponse_base64" | base64 -d | xmllint --format -`, a copy-paste comment-injection payload, named tools with specific usage ("SAML Raider → 'XSW Test' → cycle through all 8 variants"), and a step-by-step PoC pattern. It falls short of 5 because the XSW1 XML uses schematic placeholders ("..."), XSW2-8 mechanics are deferred entirely to the tool, and no command shows how to re-encode/re-submit a crafted SAMLResponse.

4 / 5

Workflow Clarity

Section 11's PoC pattern is a clear 7-step sequence with an explicit success check ("Any variant that returns logged-in-as-target = bug") and fallback loops ("If XSW fails, try comment injection... If still fails, try signature stripping"), so the destructive-operation cap does not apply. Not a 5 because the workflow lacks a validate→fix→retry checkpoint structure (e.g., how to verify the crafted message decodes/re-encodes correctly before submitting, or how to document the resulting session beyond a vague step 7).

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and the "Cross-references" section points to `skills/_corpus/payloads/SAML Injection/` paths outside this bundle that are not navigable files within it. The 145-line body is well-sectioned but monolithic — detailed XSW variants, severity calibration, exemplar CVEs, and remediation are all inline where a references/ file split would fit. This matches the anchor of some structure with references that are present but not clearly signaled/useful.

3 / 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, well-scoped description with strong distinctiveness and good trigger terms, weakened only by the complete absence of a "when to use" clause and slight under-coverage of the attack classes the body actually teaches. Adding a "Use when auditing/testing SAML SSO..." sentence would resolve the main gap.

Suggestions

Add an explicit trigger clause, e.g. "Use when testing or auditing SAML-based SSO logins, SAMLRequest/SAMLResponse parameters, or enterprise IdP/SSO bug bounty targets."

Mention the remaining attack classes covered by the body (replay, KeyInfo/certificate confusion, SAMLRequest vs SAMLResponse confusion) so the description fully represents the skill's scope.

Include the natural synonyms "SSO" and "single sign-on" as trigger terms since users hunting this skill will often phrase it that way.

DimensionReasoningScore

Specificity

The description enumerates five concrete, named techniques — "XSW (XML Signature Wrapping) variants 1-8, comment injection, signature stripping, assertion forgery, IdP metadata abuse" — which is specific and actionable. It falls short of a 5 because the body covers additional attack classes (replay, KeyInfo/certificate confusion, SAMLRequest/Response confusion) that the description omits, leaving minor gaps in coverage.

4 / 5

Completeness

The "what" is clear (a catalog of SAML 2.0 attack techniques), but there is no "Use when..." clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the "what" is concrete and detailed, and not a 4 because the "when" is entirely absent rather than merely implicit.

3 / 5

Trigger Term Quality

Natural keywords a user would say are present: "SAML 2.0", "XML Signature Wrapping", "assertion", "signature", "IdP". It is not a 5 because common variations like "SSO", "single sign-on", "SAMLResponse", or "bounty" phrasing are missing from the description itself (the when_to_use metadata is not part of the evaluated description).

4 / 5

Distinctiveness Conflict Risk

"SAML 2.0 attacks — XSW (XML Signature Wrapping) variants 1-8..." carves out a clear niche with distinct trigger terms (SAML, XSW, assertion, IdP); virtually no other skill would collide with these terms. This clearly matches the anchor 5 example of a clear niche with 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/saml/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.