setup-browser-cookies

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real Chromium browser into a headless browse session. This eliminates manual login steps for QA tests by reusing authenticated cookies.

Core Features & Use Cases

  • Import cookies from Chromium-based browsers into a Playwright/session environment.
  • Interactive picker UI to choose domains to import, enabling quick QA testing on authenticated pages.
  • Works as a bridge between real browser sessions and headless test runners.

Quick Start

Open the cookie picker, select which cookie domains to import, and start your 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 Playwright headless session?

To import cookies into a headless session, this skill bridges real Chromium browser cookies into Playwright environments, using an interactive domain picker UI to load selected authenticated cookies for QA testing.

Can I reuse existing login cookies for QA testing without re-authenticating?

Yes, reusing login cookies for QA testing is the core use case; the skill imports existing authenticated Chromium cookies into headless sessions, eliminating manual login steps and streamlining automated test workflows.

Does this cookie import tool work with Chromium-based browsers?

Yes, the cookie import mechanism works with Chromium-based browsers, extracting real session cookies and loading them into headless environments via an interactive domain picker for authenticated page testing.

How do I select specific cookie domains to import for headless testing?

To select specific cookie domains, the skill presents an interactive picker UI where you choose which authenticated domains to import, then loads only those selected cookies into the headless browser session.

Why do my headless browser tests fail on authenticated pages?

Headless browser tests fail on authenticated pages because they lack session cookies; this skill solves that by importing real Chromium login cookies into the headless environment, bypassing the need for re-authentication.

What's the best way to test authenticated pages in a headless browser?

The best way to test authenticated pages in headless browsers is importing real Chromium cookies via an interactive domain picker, directly loading existing session cookies into the Playwright environment without re-authenticating.