setup-browser-cookies

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real Chromium browser into a headless browser session to enable authenticated QA testing without manual logins.

Core Features & Use Cases

  • Import cookies for selected domains into a headless test session.
  • Use during QA to simulate logged-in user workflows across sites.
  • Interactive picker UI to choose which domains to import and apply them to the session.

Quick Start

Open the cookie picker, select the domains to import, and start your headless session with the imported cookies.

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 headless session for QA testing?

You can import real browser cookies into a headless session by using an interactive domain picker to select specific cookies from your local Chromium browser and apply them directly to your automated test environment.

What is the benefit of importing cookies for headless automation?

Importing cookies for headless automation allows you to simulate authenticated user workflows and test protected pages without needing to script manual login processes for every test run.

Can I use this to bring cookies from a real Chromium browser into headless tests?

Yes, this specifically imports cookies from a real Chromium browser into a headless browsing session, allowing you to bypass authentication and access logged-in states during QA testing.

How do I select which domains to apply cookies for during automated testing?

You select which domains to apply cookies for by using the interactive domain picker UI, which lets you choose exactly which authenticated domain sessions to load into your headless browser.

Do I need to manually log in before running headless browser tests?

No, you do not need to manually log in before running headless browser tests because you can import existing authenticated cookies from your real Chromium browser directly into the test session.

Does this approach work with cookies from browsers other than Chromium?

This approach specifically supports importing cookies from real Chromium browsers, meaning you must have a local Chromium-based browser installed to extract the cookies for your headless session.