setup-browser-cookies

Import Chromium cookies into a Playwright session via an interactive picker.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real Chromium browser into the headless browse session to enable authenticated QA testing without manual login steps.

Core Features & Use Cases

  • Interactive cookie picker UI to choose which domains to import.
  • Decrypt and load cookies into the Playwright session for deterministic test runs.
  • Verify cookies and reuse across test steps, including login-required pages.

Quick Start

Open the cookie picker, select the domains to import, then tell me you're done.

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 Playwright headless tests?

To import browser cookies into Playwright, use the interactive picker UI to select specific cookie domains from your real Chromium browser, decrypt them, and load them into the headless session for deterministic, authenticated test runs without manual logins.

Why do my Playwright QA tests fail on login-required pages in headless mode?

Playwright QA tests fail on login-required pages in headless mode because the session lacks authentication state. Importing real Chromium browser cookies into the headless session provides the necessary authenticated context to bypass manual login steps and access restricted pages.

Does importing cookies from a real Chromium browser work for headless automation?

Yes, importing cookies from a real Chromium browser works for headless automation by locating the browser binary, decrypting the stored cookies, and loading the selected domains into the Playwright session to enable authenticated, deterministic test execution.

What is the best way to achieve deterministic QA testing without manual login steps?

The best way to achieve deterministic QA testing without manual logins is importing real browser cookies into headless Playwright sessions. An interactive picker UI lets you choose which cookie domains to load, verifying imported domains to ensure consistent authenticated test runs.

Can I choose which cookie domains to import for my automation tests?

Yes, you can choose which cookie domains to import using an interactive picker UI. After selecting the desired domains, the Skill decrypts the cookies from your real Chromium browser and loads them directly into your Playwright session for immediate use in test runs.

What are the limitations of using imported browser cookies for headless testing?

Imported browser cookies for headless testing requires locating the Chromium browser binary and decrypting its cookie store. Cookies may expire or become invalid, requiring re-importation, and this approach is limited to Chromium-based browsers for Playwright session authentication.