setup-browser-cookies

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Import cookies from a real Chromium browser into the headless browse session. This lets automated tests start with an authenticated state without manual login steps.

Core Features & Use Cases

  • Interactive cookie picker: choose which domains to import into the headless session.
  • Pre QA readiness: ensure authenticated pages load with correct cookies during testing.
  • Direct import path: import cookies by domain when you know the target domain.

Quick Start

Open the cookie picker, select domains to import, and verify that cookies are loaded in 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 Chromium test session?

To import browser cookies into a headless session, open the interactive cookie picker, select the desired domains, and verify decryption and loading into the automation environment for QA testing.

Can I select specific cookie domains to import for automated QA testing?

Yes, you can select specific cookie domains to import using an interactive picker UI before starting your headless browse session, ensuring only targeted authenticated pages load during testing.

Do I need to build the cookie picker before importing headless browse session cookies?

Yes, importing real Chromium browser cookies requires a one-time build of the interactive cookie picker and direct browser access to decrypt and load cookies into the headless session.

Why use real browser cookies in headless automation instead of manual login steps?

Using real browser cookies in headless automation lets automated tests start with an authenticated state without manual login steps, ensuring QA readiness for authenticated pages during testing.

What's the best way to test authenticated pages with headless browser automation?

The best way to test authenticated pages is importing cookies from a real Chromium browser into the headless session by domain, bypassing manual login steps and verifying authenticated page loads.

Are there limitations when importing cookies into a headless browse session for QA testing?

Limitations include requiring a one-time build of the cookie picker, direct browser access to decrypt Chromium cookies, and integration with the browser automation environment to load them successfully.