setup-browser-cookies

Import Chromium browser cookies into a headless browser session.

1|Updated May 8, 2026
One-click install
npx skills add https://github.com/npc-chris/dfn-discovery --skill setup-browser-cookies-npc-chris
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/npc-chris/dfn-discovery/tree/main/.agents/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/npc-chris/dfn-discovery --skill setup-browser-cookies-npc-chris

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manages the import of cookies from a real Chromium browser into a headless browser session for authenticated browsing and QA testing.

Core Features & Use Cases

  • Import Browser Cookies: Transfers cookies from your actual Chromium browser into a headless browsing environment.
  • User Interactive Selection: Offers an interactive picker for users to choose which cookie domains to import.
  • Use Case: Before testing authenticated pages, use this skill to import the necessary cookies to maintain a consistent browsing context.

Quick Start

Run the setup-browser-cookies skill to import cookies from your current 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 browser cookies into a headless browser for automated QA testing?

To import browser cookies for automated QA testing, this skill transfers cookies from your actual Chromium browser into a headless browsing environment to maintain an authenticated session context.

Can I choose specific cookie domains to migrate to a headless browser?

Yes, you can choose specific cookie domains to migrate. This skill offers an interactive picker allowing you to select exactly which cookie domains to import into your headless browser session.

What do I need to set up authenticated browsing sessions in a headless environment?

To set up authenticated browsing sessions, you need both a real browser and a headless browser environment functioning together, and the process may interact with external tools like cookie jars and authentication providers.

Why do my headless browser tests fail on authenticated pages?

Headless browser tests fail on authenticated pages because they lack your active session context. You resolve this by migrating cookies from your real Chromium browser before testing to establish authenticated browsing.

Does this cookie import process work with non-Chromium browsers?

The cookie import process is designed specifically to facilitate cookie migration from a real Chromium browser, meaning it currently targets Chromium browser environments for transferring authenticated browsing sessions.