setup-browser-cookies

Import and decrypt Chromium cookies into a headless session.

5|1|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/forbotsake/forbotsake --skill setup-browser-cookies-forbotsake
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/forbotsake/forbotsake/tree/main/.claude/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/forbotsake/forbotsake --skill setup-browser-cookies-forbotsake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real Chromium browser into the headless browse session, enabling authenticated QA without repeated sign-ins.

Core Features & Use Cases

  • Interactive cookie picker UI to select domains to import.
  • Import and decrypt cookies into the headless session for immediate testing.
  • Use before QA testing authenticated pages and to preserve session state across runs.

Quick Start

Open the cookie picker and import the domains you need, then run your tests with the loaded sessions.

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 Playwright headless tests?

To import real browser cookies into Playwright headless tests, use an interactive cookie picker UI to select target domains, decrypt stored Chromium cookies, and load them into your headless session for immediate authenticated QA testing.

Can I preserve session state across multiple headless browser runs?

Yes, you can preserve session state across multiple headless browser runs by importing decrypted cookies from your real Chromium browser into the headless session before executing your QA tests.

Does importing Chromium cookies into headless sessions require domain-level selection?

Yes, importing Chromium cookies into headless sessions requires domain-level selection. You use an interactive cookie picker UI to specify and import only the chosen domains, preventing unnecessary session data from loading.

What's the best way to handle authenticated pages in headless QA testing?

The best way to handle authenticated pages in headless QA testing is importing decrypted cookies from a real Chromium browser into the headless session, bypassing repeated sign-ins and enabling immediate access to protected routes.

Why do headless browser tests fail to retain login sessions without imported cookies?

Headless browser tests fail to retain login sessions because they start with an empty state. Importing decrypted cookies from your real Chromium browser into the headless session resolves this by restoring the required authentication tokens.