setup-browser-cookies

Import Chromium cookies into a headless browser session via an interactive picker.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/EhsaanArk/ai-signal-router --skill setup-browser-cookies-ehsaanark
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/EhsaanArk/ai-signal-router/tree/main/.claude/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/EhsaanArk/ai-signal-router --skill setup-browser-cookies-ehsaanark

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MANUAL TRIGGER ONLY: invoke only when user types /setup-browser-cookies. Import cookies from your real Chromium browser into the headless browse session. 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

  • Interactive cookie picker: import cookies from your real browser into a headless session.
  • Domain-scoped import: selectively choose which cookie domains to load.
  • QA readiness: prepare authenticated pages for testing by preloadin gcookies.

Quick Start

Trigger the browser cookies setup by typing /setup-browser-cookies and follow the interactive picker to import domains before QA testing authenticated pages.

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 from my real browser into a headless session for QA testing?

You import cookies by triggering the interactive setup flow, which opens a picker UI to selectively load real Chromium browser cookies by domain for authenticated QA testing workflows.

What is the best way to authenticate a headless browser for testing authenticated pages?

The best way to authenticate a headless browser is importing real login cookies from your Chromium browser using an interactive domain picker, preparing the session for authenticated QA testing.

Can I selectively choose which cookie domains to load into my headless test session?

Yes, you can selectively choose cookie domains to load through the interactive picker UI, which allows domain-scoped importing of cookies from your real Chromium browser into the headless session.

Does importing browser cookies into a headless session require any manual trigger?

Yes, importing browser cookies requires a manual trigger; you must explicitly invoke the setup command to start the interactive domain picker and load the authentication cookies.

When do I need to set up browser cookies for headless QA testing?

You need to set up browser cookies for headless QA testing when simulating browsers with real login cookies across multiple domains to enable authenticated flow testing.