setup-browser-cookies

Import cookies from Chromium-based browsers into Playwright sessions.

Updated Oct 15, 2025
One-click install
npx skills add https://github.com/vibrationalforce/Echoelmusic --skill setup-browser-cookies-vibrationalforce
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/vibrationalforce/Echoelmusic/tree/main/.claude/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/vibrationalforce/Echoelmusic --skill setup-browser-cookies-vibrationalforce

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing authenticated test states across multiple browsers is tedious and flaky; this skill automates importing cookies from your real browsers into a headless session for reliable QA.

Core Features & Use Cases

  • Interactive domain cookie import: select which domains to import from multiple browsers.
  • Browser compatibility: supports Comet, Chrome, Arc, Brave, and Edge for seamless QA testing.
  • Headless session integration: loads imported cookies into Playwright sessions for authenticated tests.

Quick Start

Run the setup to locate your browser, open the cookie picker, then select the domains you want to import.

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 into a Playwright headless session for QA testing?

To import cookies into a Playwright headless session, this skill locates your real browser binary, launches an interactive picker to select specific cookie domains, and verifies the imported cookies are available for your authenticated tests.

Can I import cookies from Arc or Brave into headless browser tests?

Yes, you can import cookies from Arc and Brave into headless browser tests, along with Chrome, Edge, and Comet, by selecting the desired cookie domains through the interactive picker UI before running your QA session.

What's the best way to manage authenticated test states across multiple browsers?

Managing authenticated test states across multiple browsers is automated by importing cookies from your real Chromium-based browsers directly into a headless Playwright session, eliminating the flakiness of manual authentication setups.

How do I select specific cookie domains to import for headless QA?

You select specific cookie domains to import for headless QA by running the setup flow to locate your browser binary, opening the provided interactive picker UI, and choosing the exact domains needed for your test session.

Does setup-browser-cookies support Chromium-based browsers for cookie import?

Yes, setup-browser-cookies supports detected Chromium-based browsers including Chrome, Arc, Brave, Edge, and Comet, automatically locating the browser binary to facilitate seamless cookie import into headless QA sessions.