setup-browser-cookies

Import decrypted browser cookies into Playwright headless testing sessions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real Chromium browser (Comet, Chrome, Arc, Brave, Edge) into the headless browse session. Opens an interactive picker UI where you select which cookie domains to import. Use before QA testing authenticated pages.

Core Features & Use Cases

  • Interactive browser cookie picker to select domains for import into headless sessions.
  • Decrypt and load cookies into the Playwright-based testing environment for immediate use.
  • Works with multiple browsers (Comet, Chrome, Arc, Brave, Edge) to streamline QA workflows.

Quick Start

Start the gstack cookie-import flow by running the setup-browser-cookies command, then follow the interactive UI prompts to import domains.

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

To import browser cookies into a headless Playwright session, run the setup-browser-cookies command to launch an interactive picker UI. This decrypts and loads selected cookie domains from your local browser store directly into the headless testing environment.

Can I use cookies from Chrome or Arc for authenticated headless browser testing?

Yes, authenticated headless browser testing supports importing cookies from multiple Chromium browsers, including Chrome, Arc, Brave, Edge, and Comet. The interactive picker lets you select which specific cookie domains to decrypt and load into your session.

What is the best way to test authenticated pages in headless automation without manually logging in?

The best way to test authenticated pages in headless automation is importing decrypted cookies from a real browser store. This bypasses manual login by loading existing authenticated session cookies directly into the Playwright testing environment via an interactive domain picker.

Does importing cookies into Playwright require a specific local browser cookie store?

Yes, importing cookies into Playwright requires a local Chromium browser cookie store and a compatible headless browser runner. A one-time readiness check locates the cookie store and launches the interactive picker to select domains for decryption and loading.

Why do I need to select specific cookie domains before running automated QA tests?

Selecting specific cookie domains before running automated QA tests ensures only the relevant authenticated sessions are imported. The interactive picker UI scans your local browser cookie store, letting you choose exact domains to decrypt and load into the headless environment.

Are there limitations when using imported browser cookies for headless QA testing workflows?

Limitations include requiring a local Chromium browser cookie store and a compatible headless runner like Playwright. A one-time readiness check is mandatory to locate the store, and cookies must be decrypted and loaded per selected domain before testing authenticated pages.