hunt-clickjacking

Hunt Clickjacking — missing X-Frame-Options / CSP frame-ancestors lets an attacker embed the target page in an invisible iframe and trick victims into clicking buttons they cannot see (UI redressing). Targets: login flows, money transfers, account settings, OAuth confirmation pages. Confirm by fetching the page, then PROVE it frames in a real browser and a sensitive state-changing action survives the cross-site context (SameSite cookies / framebusting JS can defeat it) — header-absence alone is not a finding.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

92%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 efficient, highly actionable testing guide with copy-paste PoC material and a clearly sequenced, validation-driven workflow. The only minor slack is the conceptual intro that restates known material already present in the description.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and actionable, but the "## What is Clickjacking" intro and the "Highest-value targets" list explain a concept Claude already knows and partly duplicate the description, so it is not fully trimmed.	4 / 5
Actionability	Copy-paste-ready commands like `curl -sI https://target.example/account/transfer \| grep -iE 'x-frame-options\|content-security-policy'` and a complete PoC `<iframe>` HTML snippet cover the common cases fully.	5 / 5
Workflow Clarity	A clear two-step sequence (screening then prove) is paired with an explicit "Confirm ALL of the following, or it is not exploitable" validation checklist and a stop condition ("If either is present... stop"), giving explicit validation checkpoints.	5 / 5
Progressive Disclosure	The skill is self-contained and well-organized into clear sections (Protection Headers, How to Test, False Positives, Proof Requirements) with no need for external references and no nested file references.	5 / 5
	Total	19 / 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-targeted description that names concrete testing actions and a clear niche, but it lacks an explicit "Use when..." trigger clause, capping its completeness. Slightly verbose in narrative form where a tighter action list would help.

Suggestions

Add an explicit "Use when..." trigger clause (e.g., "Use when testing for clickjacking/UI redressing or when a user reports missing X-Frame-Options or frame-ancestors headers") to raise completeness above 3.

Include natural trigger phrases a reporter might say ("clickjacking test", "frame-ancestors missing", "can this page be iframed") to broaden trigger-term coverage.

Convert the narrative phrasing into a tighter comma-separated action list to reduce verbosity while preserving the concrete steps.

Dimension	Reasoning	Score
Specificity	Phrases like "embed the target page in an invisible iframe", "fetching the page", and "PROVE it frames in a real browser" name several concrete actions, but they are delivered narratively rather than as a comprehensive action list, keeping it just below 5.	4 / 5
Completeness	The "what" is clear (hunt clickjacking, prove framing), but there is no explicit "Use when..." trigger clause; "when" is only weakly implied via the "Targets:" list, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	"Clickjacking", "X-Frame-Options", "CSP frame-ancestors", "UI redressing", and "SameSite cookies" are natural domain keywords with a synonym pair (Clickjacking/UI redressing), but a few common reporter phrasings are missing.	4 / 5
Distinctiveness Conflict Risk	"Hunt Clickjacking" occupies a narrow, specific vulnerability niche with distinct technical triggers (frame-ancestors/X-Frame-Options) and minimal overlap risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: elementalsouls/Claude-BugHunter
Path: skills/hunt-clickjacking/SKILL.md
Commit: d4b54e1

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.