dismiss-overlays

Dismiss cookie banners and consent overlays before DOM extraction or screenshots.

2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/aemcoder/skills --skill dismiss-overlays
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dismiss-overlays
Source: https://github.com/aemcoder/skills/tree/main/skills/migration/dismiss-overlays
Command: npx skills add https://github.com/aemcoder/skills --skill dismiss-overlays

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and scripts (resource) components.

What problem does it solve?

This Skill removes or dismisses page overlays (like cookie banners, GDPR/CCPA consent, and chat widgets) that block content extraction or visual verification.

Core Features & Use Cases

  • Overlay detection via screenshot verification: Takes a full-page screenshot to determine whether overlays are present, then verifies cleanup after dismissal/removal.
  • Best-effort vendor-specific dismissal: Uses heuristic selectors to click vendor “accept/dismiss” controls when available so consent cookies are set properly.
  • Fallback DOM removal for non-dismissible overlays: Removes overlays as a last resort, including fixed high-z-index elements, and re-checks cleanliness.
  • Safety-minded cleanup: Deletes temporary screenshots after completion so no artifacts persist downstream.
  • Use case: Before running a migration or scraping workflow, run this Skill on a URL that shows cookie/GDPR banners to ensure subsequent DOM extraction or screenshot comparisons are accurate.

Quick Start

Run dismiss-overlays against a target {tabId} to detect and clear cookie/consent overlays before you extract the DOM or take full-page screenshots.

Frequently Asked Questions about dismiss-overlays

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I remove cookie banners blocking web scraping with Playwright?

Remove cookie banners blocking web scraping by applying vendor heuristic click logic to set consent cookies, falling back to DOM removal for non-dismissible overlays to ensure accurate DOM extraction. It verifies cleanup using full-page screenshots.

Why does a GDPR consent overlay prevent full-page screenshots in browser automation?

A GDPR consent overlay prevents full-page screenshots because fixed high-z-index elements obstruct the underlying DOM content. This Skill detects these overlays via screenshots and clears them so visual capture proceeds without interference.

Can I dismiss chat widgets and cookie banners before migrating a website?

Yes, you can dismiss chat widgets and cookie banners before website migration by running this Skill on a target tabId. It clears obstructive overlays and deletes temporary artifacts so subsequent DOM extraction remains accurate.

What is the best way to handle non-dismissible cookie popups during automated browsing?

The best way to handle non-dismissible cookie popups is clicking vendor accept controls to set consent cookies, then falling back to direct DOM removal of fixed elements if clicks fail, verifying cleanliness with bounded retries.

Does clearing overlays delete temporary screenshots created during the detection process?

Yes, clearing overlays deletes temporary screenshots created during the detection process. This safety-minded cleanup ensures no visual artifacts persist downstream after the cookie banners and consent overlays are successfully dismissed.