setup-browser-cookies

Import Chromium browser cookies into a headless session for authenticated QA testing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real Chromium browser into the headless browse session so QA and automation can run against authenticated pages without manual login.

Core Features & Use Cases

  • Import cookies from a real browser into a headless session for automated QA tests.
  • Open an interactive picker UI to select which cookie domains to import.
  • CDP awareness ensures cookies are only imported when needed and avoids duplicating sessions.

Quick Start

Open the cookie picker UI, select the domains you want 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 a headless session for QA testing?

To import cookies into a headless session, you open the interactive domain picker UI, select the desired cookie domains, and confirm completion to inject the authenticated state directly into your automation environment.

Can I use real Chromium cookies for automated authentication in headless browser automation?

Yes, you can use real Chromium cookies for automated authentication in headless browser automation by importing them, which allows QA tests to bypass manual login and run directly against authenticated pages.

Does this cookie import process check if a CDP session already exists?

Yes, the cookie import process includes a CDP check to verify existing sessions, ensuring cookies are only imported when needed and avoiding the duplication of active authenticated headless browser sessions.

What is the best way to select specific cookie domains for a headless automation task?

The best way to select specific cookie domains for headless automation tasks is using the interactive picker UI, which lets you manually choose exactly which authenticated domains to import into the headless session.

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

Headless automation tests fail on authenticated pages because headless sessions lack your real browser's session tokens; importing real Chromium cookies into the headless session injects the necessary authenticated state to resolve this.