setup-browser-cookies

Import cookies from real Chromium browsers into headless sessions for QA testing.

Updated Jun 9, 2026
One-click install
npx skills add https://github.com/ericdahl-dev/coauthor-cleaner --skill setup-browser-cookies-ericdahl-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/ericdahl-dev/coauthor-cleaner/tree/main/.claude/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/ericdahl-dev/coauthor-cleaner --skill setup-browser-cookies-ericdahl-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires puppeteer, playwright, and includes scripts (resource) and assets (resource) components.

What problem does it solve?

This Skill facilitates the import and management of cookies from real browsers into headless browser sessions, simplifying authenticated interactions with web applications during testing and QA.

Core Features & Use Cases

  • Import Cookies: Transfer cookies from your regular browser to a headless browser session.
  • Session Management: Configure and maintain sessions for authenticated web interactions.
  • Use Case: Before conducting QA tests on a website that requires login, use this Skill to import your existing browser cookies to ensure the headless browser operates with the correct session information.

Quick Start

Use the setup-browser-cookies skill to import cookies from your browser for testing on 'example.com'.

Frequently Asked Questions about setup-browser-cookies

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

FAQPage Schema
How do I import cookies from my real browser into a headless browser session for QA testing?

To import cookies for QA testing, this Skill parses cookie data from your regular Chromium browser and configures the headless session with the correct authentication state. It automates session synchronization to simplify authenticated web interactions.

Can I use this cookie management approach with Puppeteer and Playwright?

Yes, this cookie management approach works with Puppeteer and Playwright. It handles cookie parsing and session setup specifically for browser automation tools, enabling authenticated headless browser sessions during testing workflows.

What is the best way to handle session synchronization between real browsers and headless sessions?

Session synchronization between real browsers and headless sessions is best handled by transferring existing cookies into the automation environment. This Skill manages that session setup, allowing headless browsers to operate with your active login information.

Why do my headless browser automation tests fail on authenticated pages?

Headless browser automation tests fail on authenticated pages because the session lacks valid login cookies. Importing cookies from your real browser into the headless session resolves this by providing the required authentication state for QA testing.

Do I need to manually log in during headless browser testing if I import cookies?

No, you do not need to manually log in during headless browser testing if you import cookies. By transferring your existing session cookies to the headless browser, the automation tool operates with the correct authentication state automatically.