setup-browser-cookies

Import selected Chromium cookie domains into a headless browse session.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real Chromium browser into the headless browse session. This enables authenticated QA workflows without needing to re-login for every test run.

Core Features & Use Cases

  • Interactive cookie-domain picker to import cookies into a headless session
  • Support selecting which domains to import for authenticated QA pages
  • Streamlines QA by preserving login state across test steps

Quick Start

Open the interactive cookie picker and import the domains you use for authenticated QA sessions.

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 browser session for QA testing?

You can import real-browser cookies into a headless browser session using an interactive picker UI to select specific cookie domains, enabling authenticated QA workflows without needing to re-login for every test run.

Why do I need to import cookies for headless browser automation?

Importing cookies for headless browser automation preserves your login state across test steps, streamlining QA workflows by allowing direct access to authenticated pages without repeatedly performing login operations during each test run.

Can I select specific cookie domains to import into my headless test environment?

Yes, you can select specific cookie domains to import into your headless test environment using an interactive cookie-domain picker UI, ensuring only the necessary authenticated sessions are transferred before testing.

Does importing browser cookies into headless tests work with gstack?

Yes, the cookie import workflow for headless tests is fully integrated with gstack, running directly in a headless browser context to facilitate authenticated QA testing sessions.

What is the best way to test authenticated pages in a headless browser without re-logging in?

The best way to test authenticated pages in a headless browser without re-logging in is importing real Chromium browser cookies into the headless session, preserving the login state across all subsequent test steps.