setup-browser-cookies

Import Chromium browser cookies into a headless browse session.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real Chromium browser into the headless browse session, enabling authenticated QA without manual login.

Core Features & Use Cases

  • Interactive picker UI to select cookie domains to import
  • Import cookies into the headless browser session for testing authenticated pages
  • Supports QA testing by simulating real-user sessions with imported cookies

Quick Start

Open the cookie picker, select the domains to import, and load them into the headless browser session.

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

Yes, you can test authenticated pages in headless Chromium by importing real login cookies. A Bash-driven orchestration process loads selected domain cookies into the headless session, simulating a real-user session for QA testing without requiring manual authentication steps.

What's the best way to use real login cookies for QA testing in a headless browser?

The best way to use real login cookies for QA testing is loading them from a real Chromium browser into a headless session. An interactive cookie picker UI allows you to select specific domains to import, bypassing the need to automate manual login workflows.

Does importing cookies into a headless session require environment checks?

Yes, importing cookies into a headless session requires environment checks to ensure a valid headless session is established before testing begins. This validation is part of the Bash-driven orchestration that guarantees the browser context is ready to receive imported cookies.

Can I select specific cookie domains to load into my headless browser context?

Yes, you can select specific cookie domains to load into your headless browser context using an interactive picker UI. This allows you to target exactly which authenticated sessions to import into the headless environment for focused QA testing.

Why does my headless browser session fail to test authenticated pages without importing cookies?

A headless browser session fails to test authenticated pages because it starts with empty cookies. You must import real login cookies from a Chromium browser into the headless context to simulate an authenticated real-user session and access protected pages.