setup-browser-cookies

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

10|3|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/olaafrossi/FoamPilot --skill setup-browser-cookies-olaafrossi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/olaafrossi/FoamPilot/tree/main/.claude/skills/setup-browser-cookies
Command: npx skills add https://github.com/olaafrossi/FoamPilot --skill setup-browser-cookies-olaafrossi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real Chromium browser into the headless browse session. This lets you run authenticated tests without manual login.

Core Features & Use Cases

  • Interactive picker UI to select which cookie domains to import.
  • Works with headless and real browsers to maintain session continuity during tests.
  • Use before QA testing authenticated pages to ensure a consistent login state.
  • Use case: QA automation runs against a site with domain-based cookies loaded from your browser.

Quick Start

Run the cookie import flow and use the interactive picker to select domains, then confirm when done.

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

An interactive picker UI lets you choose specific cookie domains from your real Chromium browser to import into the headless session. This maintains session continuity for authenticated QA testing without requiring manual login steps.

Why does my headless browser test fail to authenticate on pages requiring login?

Headless browser tests fail authentication because they lack existing session cookies. Importing cookies from your real Chromium browser into the headless session resolves this by transferring the authenticated state directly without manual login.

Can I select specific cookie domains to import for headless browser testing?

Yes, you can select specific cookie domains using an interactive picker UI before importing them into the headless browse session. This ensures only the necessary authenticated cookies are loaded for your targeted QA testing.

Does this cookie import method work with Chromium browsers and Playwright?

The cookie import flow works with real Chromium browsers and headless browse sessions to maintain session continuity. It uses a Bash workflow to transfer cookies for QA testing authenticated pages.

Do I need to manually log in before running authenticated tests with imported cookies?

No, you do not need to manually log in before running authenticated tests. Importing cookies from your real Chromium browser into the headless session provides a consistent login state automatically.