setup-browser-cookies

Import Chromium browser cookies into headless sessions for authenticated QA testing.

1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/apeejay-education/cadencesprout --skill setup-browser-cookies-apeejay-education
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/apeejay-education/cadencesprout/tree/main/.agents/skills/gstack-setup-browser-cookies
Command: npx skills add https://github.com/apeejay-education/cadencesprout --skill setup-browser-cookies-apeejay-education

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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 UI to select which cookie domains to import
  • Persist cookies across commands for seamless authenticated sessions
  • Supports headless browser sessions during QA testing

Quick Start

Open the cookie picker, import domains you want, then run tests with the authenticated browser 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 cookies into a Playwright headless browser for QA testing?

You can import cookies into a Playwright headless browser by loading them from a real Chromium session. This skill decrypts and injects cookies to recreate authenticated states for QA testing without requiring manual re-login.

What's the best way to authenticate a headless browser for automation without re-login?

Authenticating a headless browser for automation is best handled by importing existing cookies from your real Chromium profile. This skill decrypts and persists them across commands to maintain authenticated QA sessions.

Can I select specific domains when importing browser cookies for headless sessions?

Yes, you can select specific domains when importing browser cookies. This skill opens an interactive picker UI where you choose exactly which cookie domains to load into the headless session.

Does importing cookies persist authenticated states across multiple automation commands?

Importing cookies does persist authenticated states across commands. This skill ensures your decrypted Chromium cookies remain active throughout your headless QA testing session for seamless automation.

Why do I need to import cookies for headless QA testing instead of logging in normally?

Importing cookies for headless QA testing avoids the overhead of automated login scripts and two-factor authentication flows. It allows you to quickly recreate signed-in states for debugging and testing.

How do I decrypt Chromium cookies to use in a headless browser session?

To decrypt Chromium cookies for a headless browser session, you extract them from your local browser profile. This skill handles the decryption and loading process to enable authenticated automation.