setup-browser-cookies

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

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/jeisenback/original-curse-killer --skill setup-browser-cookies-jeisenback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/jeisenback/original-curse-killer/tree/main/.claude/skills/setup-browser-cookies
Command: npx skills add https://github.com/jeisenback/original-curse-killer --skill setup-browser-cookies-jeisenback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real browser into the headless browse session to enable authenticated QA testing without repeated logins.

Core Features & Use Cases

  • Interactive browser cookie picker that lists available cookie domains.
  • Supports major browsers (Comet, Chrome, Arc, Brave, Edge) and imports selected domains.
  • Seamlessly loads cookies into the headless session for immediate authenticated testing.

Quick Start

Run the cookie picker to detect installed browsers and import the domains you want.

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

You import browser cookies by running an interactive cookie picker that detects installed browsers, lists available cookie domains, and loads selected domains directly into the headless browsing context for authenticated QA testing.

Can I load cookies from Chrome or Brave into a headless browser context?

Yes, you can load cookies from major browsers including Chrome, Brave, Arc, Comet, and Edge into a headless browser context by selecting the desired cookie domains via the interactive cookie picker.

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

You need to import cookies for headless browser testing to simulate a signed-in user environment across multiple domains, enabling authenticated QA steps without manually performing login workflows for every test session.

Do I need a cookie picker binary to use headless browser cookies?

Yes, a cookie picker binary is required to identify cookies from your real browser and import selected domains into the headless browsing context for secure handling of sensitive session data.

Are there limitations when simulating a signed-in user environment with imported cookies?

Limitations include the need for secure handling of sensitive data and per-session cookie resets, meaning imported cookies must be reloaded for each new headless session and selected at the domain level.