setup-browser-cookies

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

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/amanik/sailor-score-debug --skill setup-browser-cookies-amanik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/amanik/sailor-score-debug/tree/main/.claude/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/amanik/sailor-score-debug --skill setup-browser-cookies-amanik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real Chromium browser into the headless browse session to enable authenticated QA tests without manual logins.

Core Features & Use Cases

  • Interactive cookie picker to select which cookie domains to import for a headless session.
  • Decrypts and loads the chosen cookies into the headless browser for immediate testing.
  • Supports use cases where automated QA requires runtime-authenticated pages.

Quick Start

Open the cookie picker, select the domains to import, then confirm.

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 cookies into a headless browser for QA testing?

You can import cookies into a headless browser by selecting cookie domains through an interactive picker, which decrypts and loads them to preload login states for authenticated QA tests.

What is the best way to preload login states for automated QA tests?

The best way to preload login states is importing cookies from a real Chromium browser into a headless session, bypassing manual logins by selecting the relevant authenticated domains.

Can I select specific cookie domains to load into my headless browser session?

Yes, you can select specific cookie domains to load into your headless browser session using an interactive cookie picker that decrypts and imports only the chosen authenticated states.

Does importing browser cookies require decrypting them from the real Chromium browser?

Yes, importing browser cookies requires decrypting them from the real Chromium browser before loading the selected cookie domains into the headless browser session for runtime testing.

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

You need to import cookies for headless browser automation to enable authenticated QA testing without manual logins, allowing automated scripts to access runtime-authenticated pages immediately.

When should I use a cookie importer instead of manual login for QA testing?

Use a cookie importer instead of manual login when automated QA requires runtime-authenticated pages, allowing you to preload login states by selecting cookie domains through an interactive picker.