CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clickjacking

UI redressing — missing X-Frame-Options / frame-ancestors, frame-buster bypass, drag-and-drop, cursorjacking, double-clickjacking, and sensitive-action framing.

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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, expert-level playbook: executable detection commands, a thorough misconfig-to-exploit matrix, working PoCs, and an explicit decision gate with a checklist. The only real weaknesses are two truncated variant PoCs and a dangling cross-reference to 'finding-protocol' with no bundle file behind it.

DimensionReasoningScore

Conciseness

The ~105-line playbook is lean throughout: a two-line framing of the attack, then immediately a curl detection loop, a compact misconfig matrix, PoC code, chains, tools, and a decision gate. No padding, no explanation of concepts Claude already knows, and every section earns its place.

5 / 5

Actionability

The header-inspection loop and the main overlay PoC are copy-paste ready (with a sensible <TARGET> placeholder), and the misconfig matrix maps each class to a concrete exploit. It stops short of 5 because §3.1 truncates the iframe tag with '...' and §3.2 is a one-line sketch with only a comment — two variant PoCs are incomplete.

4 / 5

Workflow Clarity

The pipeline is clearly sequenced (detect headers → classify via misconfig matrix → build PoC → chain → OPSEC) with explicit validation ('If the iframe renders the target UI → framing allowed'), bypass branches for each defense (e.g. sandbox defeating frame-busters), and a final decision-gate checklist with a conditional outcome (escalate per finding-protocol vs. downgrade to informational).

5 / 5

Progressive Disclosure

Well-organized numbered sections in a single file with no nested references, and the core playbook content arguably belongs inline. It is not a 5 because at ~105 lines the PoC variants (drag-and-drop, double-clickjacking) could live in a references/ file, and 'escalate per finding-protocol' dangles — no such file exists in the bundle, so navigation dead-ends there.

4 / 5

Total

18

/

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 distinct, technically precise description that clearly names the domain and its sub-techniques, but it reads as a topic list rather than a capability statement: it lacks action verbs, omits the headline term 'clickjacking', and has no 'Use when...' trigger clause. These gaps make it weaker for skill-selection despite strong distinctiveness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions clickjacking, UI redressing, iframe framing, or missing X-Frame-Options/frame-ancestors on sensitive pages' — this would raise completeness from 3 to 4-5.

Include the word 'clickjacking' in the description itself (currently only in name/when_to_use), since it is the phrase users most naturally say for this skill.

Convert noun-phrase topics into concrete actions, e.g. 'Detects missing X-Frame-Options/frame-ancestors, bypasses frame-busters, and builds overlay/drag-and-drop/cursorjacking PoCs' to sharpen specificity.

DimensionReasoningScore

Specificity

The description lists several concrete technique names ('frame-buster bypass, drag-and-drop, cursorjacking, double-clickjacking, sensitive-action framing') around a named domain ('UI redressing'). It falls short of a 5 because the items are noun-phrase topics rather than concrete actions — no verbs like 'detect', 'exploit', or 'generate a PoC for' — leaving minor gaps in what the skill actually does.

4 / 5

Completeness

The 'what' is clear — an inventory of UI-redressing attack surfaces — but the description contains no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 4 because 'when' is entirely absent rather than merely implicit.

3 / 5

Trigger Term Quality

Keywords are highly relevant and specific ('X-Frame-Options', 'frame-ancestors', 'cursorjacking', 'double-clickjacking'), but the single most natural user phrase — 'clickjacking' — never appears in the description itself (only in the name and when_to_use metadata). Good coverage with a few natural terms missing fits anchor 4 better than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

'UI redressing' plus named attack classes (frame-buster bypass, cursorjacking, double-clickjacking) carves out a clear niche with distinct trigger terms and minimal overlap with other skills; no generic language that would cause cross-triggering.

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