setup-browser-cookies

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real browser (Comet, Chrome, Arc, Brave, Edge) into the headless browse session. It opens an interactive picker UI where you select which cookie domains to import. Use before QA testing authenticated pages. Use when asked to import cookies, login to the site, or authenticate the browser.

Core Features & Use Cases

  • Import cookies from real browsers into a headless session for testing authenticated pages.
  • Open an interactive picker UI to select which cookie domains to import.
  • Use during QA to ensure the browser session reflects real user cookies.

Quick Start

Open the cookie picker, select the domains to import, and confirm to 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 real-browser cookies into a headless session for QA testing?

To import real-browser cookies into a headless session, use an interactive picker UI to select which cookie domains to load. This allows QA testing of authenticated pages by reflecting real user cookies in the headless browser.

Can I import cookies from Chrome or Arc into headless automation tests?

Yes, you can import cookies from real browsers like Chrome, Arc, Brave, Comet, and Edge into headless automation tests. The tool opens an interactive picker UI where you select which specific cookie domains to import.

What is the best way to test authenticated pages in headless browser automation?

The best way to test authenticated pages in headless browser automation is importing real-browser cookies into the headless session. An interactive picker UI lets you select which cookie domains to import for QA testing authenticated pages.

How does the cookie picker UI work for selecting cookies to import?

The cookie picker UI opens during headless session setup and displays available cookie domains from your real browser. You select which domains to import, confirm your selection, and the chosen cookies load into the headless session.

Do I need any special dependencies to use cookies from real browsers in headless tests?

No special dependencies are required to use cookies from real browsers in headless tests. The tool relies on standard Bash tooling and its built-in SKILL.md frontmatter to guide activation and the cookie import process.

Why import real-browser cookies instead of logging in during headless tests?

Importing real-browser cookies instead of logging in during headless tests avoids authentication flows and ensures the headless session reflects real user cookies. This streamlines QA testing of authenticated pages without handling login automation.