CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

xs-leaks

XS-Leaks — cross-site information leaks via timing, frame counting, navigation, error oracles. Side-channel attacks against same-origin authenticated state.

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/xs-leaks/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.

The body is a lean, well-organized reference with mostly executable detection code, a useful severity table, and concrete defender mitigations. Its main gaps are the absence of an explicit step sequence with validation checkpoints (verify the differential reproduces before rating severity, verify PoC across sessions) and a placeholder pseudocode snippet in the XS-Search section.

Suggestions

Add a short numbered PoC workflow with a validation checkpoint, e.g., '1. Pick a technique from section 1; 2. Build the attacker page; 3. Verify the differential reproduces across authenticated vs. unauthenticated sessions; 4. Only then rate severity per section 5.'

Replace the placeholder comment in the 1.7 XS-Search loop with executable code (e.g., a concrete timeFetch call over guessable_set with a threshold comparison).

Move the 7-category taxonomy detail into a references/ file (e.g., techniques.md), keeping SKILL.md as a concise overview that links to it, to strengthen progressive disclosure.

DimensionReasoningScore

Conciseness

The body is efficient — tight one-to-three-line technique descriptions and small runnable snippets with no padded sections or library-comparison fluff. Not 5 because the opening conceptual framing ('XS-Leaks abuse browser primitives that leak information ACROSS origins... Smaller than full cross-origin read') and the section-2 prose ('Decepticon agents should consult this...') are mild over-explanation that could be trimmed.

4 / 5

Actionability

Mostly executable guidance: the image-timing snippet, the frame-count detection code, timeFetch, and the exact defender headers (COOP/COEP/CORP, X-Frame-Options, Vary: Cookie) are concrete and runnable. Not 5 because section 1.7 is placeholder pseudocode ('// measure timing or frame-count differential') and sections 1.3, 1.5, and 1.6 give only prose directions with no code; not 3 because the majority of guidance is copy-paste ready.

4 / 5

Workflow Clarity

Section order loosely implies a process (categories -> detection -> PoC framing -> severity -> defender), but there is no explicit sequence and no validation checkpoints — e.g., nothing instructs verifying the leak differential across authenticated vs. unauthenticated sessions before rating severity, and section 4's 'Visual demonstration of leaked info' is only an implicit checkpoint. The batch ID-enumeration workflow (1.7) likewise has no verification step, consistent with the cap at 3.

3 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), and the ~110-line body is well-sectioned and self-contained, with a clearly signaled external reference (xsleaks.dev plus what it provides) and explicit cross-references to related skills. Not 5 because the body exceeds 50 lines with the full 7-category taxonomy inlined — it could be split into a references file with SKILL.md as overview; not 3 because structure is clear and nothing is buried.

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.

The description is specific and distinctive, cleanly naming the XS-Leak domain and its main attack vectors with natural trigger terms. Its main weakness is the missing 'Use when...' trigger clause — trigger keywords exist only in metadata.when_to_use, not in the description itself — which caps completeness and leaves 'when to use' implicit.

Suggestions

Append an explicit trigger clause to the description, e.g. 'Use when the user mentions xs-leaks, cross-site leaks, side-channel attacks, or detecting cross-origin information leaks in a browser.'

Add natural synonyms users say, such as 'XS-Search', 'browser side-channel', and 'cache timing', to broaden trigger term coverage.

State what the skill does with the domain (e.g., 'build and demonstrate XS-Leak PoCs, rate severity, and apply mitigations') so the description conveys actions, not just the phenomenon.

DimensionReasoningScore

Specificity

Names the domain ('XS-Leaks') and lists several concrete leak vectors — 'timing, frame counting, navigation, error oracles' — plus 'side-channel attacks against same-origin authenticated state', matching the anchor for several specific items with minor gaps. Not 5 because it describes the phenomenon's categories rather than the skill's actions (no verbs like detect, exploit, or demonstrate).

4 / 5

Completeness

The 'what' is clear and specific, but the description contains no 'Use when...' clause or equivalent explicit trigger guidance — the trigger keywords live in metadata.when_to_use rather than the description field, which caps completeness at 3 per the judging guidelines. Not 4 because 'when' is entirely absent from the description itself, not merely vague.

3 / 5

Trigger Term Quality

Includes natural terms a user would say — 'XS-Leaks', 'cross-site information leaks', 'side-channel', 'timing', 'frame counting' — giving good keyword coverage. Not 5 because common synonyms and variations are missing (e.g., 'XS-Search', 'browser', 'cache timing').

4 / 5

Distinctiveness Conflict Risk

XS-Leaks is a clear, well-defined niche with distinct triggers ('cross-site information leaks', 'side-channel', 'frame counting', 'error oracles') that would not naturally fire for any unrelated skill. Minimal conflict risk, matching the anchor exactly.

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/xs-leaks/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.