setup-browser-cookies

Import cookies from real browsers into headless sessions via an interactive picker.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real browser into the headless browse session to simulate authenticated user contexts during automated QA testing.

Core Features & Use Cases

  • Interactive picker UI to select which cookie domains to import.
  • Supports multiple browsers (Comet, Chrome, Arc, Brave, Edge) and headless sessions.
  • Use before QA testing authenticated pages or when asked to "import cookies", "login to the site", or "authenticate the browser".

Quick Start

Launch the picker, select which domains' cookies to import, and load them into the headless 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 browser cookies into a headless session for QA testing?

You can import cookies from your real browser into a headless session by launching an interactive picker UI to select specific domains and load them, allowing automated QA testing of authenticated pages.

What is the purpose of importing cookies into a headless browser?

Importing cookies into a headless browser simulates authenticated user contexts during automated QA testing, allowing you to bypass manual login steps when testing protected pages.

Can I import cookies from Chrome or Brave into a headless browsing context?

Yes, you can import cookies from multiple browsers including Chrome, Arc, Brave, Edge, and Comet directly into a headless browsing context using an interactive domain selection picker.

How do I authenticate a headless browser without manually logging in?

You authenticate a headless browser by importing existing login cookies from your real browser session, bypassing manual authentication steps when preparing to test protected web pages.

How do I select which domains to import when loading cookies into a headless session?

You select which domains to import using an interactive cookie picker UI that displays available domains, letting you choose exactly which cookies to load into the headless context.