CtrlK
BlogDocsLog inGet started
Tessl Logo

page-prep

Prepare any webpage for clean interaction by detecting and removing disruptive overlays (cookie banners, GDPR consent, modals, popups, newsletter signups, paywalls, login walls). Uses a cached database of 300+ known CMPs (Consent-O-Matic + EasyList) combined with heuristic DOM scanning. Produces portable JS recipes for any browser tool (Playwright, CDP, cmux-browser). ALWAYS use this skill before taking screenshots, scraping content, or automating interaction on any webpage that might have overlays blocking the view or preventing interaction. Triggers on: page prep, clean page, remove overlays, dismiss cookie banner, page blocked, overlay cleanup, consent banner, prepare page, unblock page, clear popups, cookie popup.

72

Quality

88%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-crafted, highly actionable skill with excellent workflow clarity including proper validation checkpoints, feedback loops, and fallback strategies. The content is thorough and provides executable code throughout, but its length (~250 lines) pushes the boundaries of conciseness — some sections like Watch Mode and format specifications could be split into reference files. The single external reference to known-patterns.md cannot be verified without bundle files.

Suggestions

Move the Watch Mode code, Detection Report Format, and Recipe Manifest Format into separate reference files to reduce the main SKILL.md length and improve progressive disclosure.

Trim explanatory paragraphs in Step 9a and 9b that explain why DOM checks miss certain things — Claude can infer this from the verification steps themselves.

DimensionReasoningScore

Conciseness

The skill is generally efficient and avoids explaining basic concepts Claude already knows, but it's quite long (~250 lines) with some sections that could be tightened. The Watch Mode code block and some explanatory paragraphs (e.g., explaining why DOM checks miss certain things) add bulk that could be trimmed. The mode table and tips section are well-structured though.

2 / 3

Actionability

The skill provides fully executable code throughout: concrete bash commands for each step, complete JS snippets for DOM checks, specific CSS selectors for close buttons, real JSON schemas for detection reports and recipe manifests, and working code for watch mode. Browser tool examples cover three different tools with copy-paste ready commands.

3 / 3

Workflow Clarity

The 10-step workflow is clearly sequenced with explicit validation checkpoints (Step 9a DOM residual check, Step 9b viewport screenshot verification), feedback loops (retry up to 2 times, fall back to hide if click fails after 5 seconds), and clear branching between thorough and quick modes. The Agent Fallback provides an ordered sequence for handling null dismiss cases.

3 / 3

Progressive Disclosure

The skill references `references/known-patterns.md` for CMP-specific patterns, which is good progressive disclosure, but no bundle files are provided to verify this reference exists. The main SKILL.md is quite long and could benefit from splitting the Detection Report Format, Recipe Manifest Format, and Watch Mode sections into separate reference files, keeping the main file as a leaner overview.

2 / 3

Total

10

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an excellent skill description that hits all the marks. It provides highly specific capabilities, comprehensive trigger terms, explicit guidance on when to use it, and occupies a distinct niche. The description is detailed without being padded, uses third person voice throughout, and would allow Claude to confidently select this skill from a large pool.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: detecting and removing overlays, cookie banners, GDPR consent, modals, popups, newsletter signups, paywalls, login walls. Also specifies the technical approach (cached database of 300+ CMPs, heuristic DOM scanning) and output format (portable JS recipes for Playwright, CDP, cmux-browser).

3 / 3

Completeness

Clearly answers both 'what' (detect and remove disruptive overlays, produce portable JS recipes) and 'when' (before taking screenshots, scraping content, or automating interaction on any webpage with overlays). Has an explicit 'ALWAYS use this skill' clause and a dedicated 'Triggers on:' list.

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would say: 'remove overlays', 'dismiss cookie banner', 'page blocked', 'clear popups', 'cookie popup', 'consent banner', 'clean page', 'prepare page', 'unblock page'. These are highly natural phrases a user would use when encountering these issues.

3 / 3

Distinctiveness Conflict Risk

Occupies a very clear niche — webpage overlay/popup removal and page preparation. The specific mention of cookie banners, GDPR consent, CMPs, paywalls, and the output format (JS recipes for browser tools) makes it highly distinguishable from general web scraping or browser automation skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
catalan-adobe/skills
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.