setup-browser-cookies

Import Chromium browser cookies into a headless session for QA testing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates importing cookies from your real Chromium browser into a headless browser session for QA testing of authenticated pages.

Core Features & Use Cases

  • Interactive picker UI to select which cookie domains to import.
  • Imports cookies into the headless session to preserve login state for automated tests.
  • Works before QA testing of authenticated pages or when prompted to "import cookies" or "authenticate the browser".

Quick Start

Launch the cookie picker and import selected domains to begin testing.

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

To import cookies into a headless browser session, use an interactive picker UI to select specific cookie domains from your real Chromium browser and load them directly into the session. This preserves login state for testing authenticated pages.

Why does my headless browser fail QA testing on authenticated pages?

Headless browser sessions lack the login state required for authenticated pages because they start without cookies. Importing cookies from your real Chromium browser into the headless session resolves this by applying your existing login state.

Can I select specific cookie domains to import into a headless Chromium session?

Yes, you can select specific cookie domains using an interactive picker UI. This allows you to choose exactly which authenticated domains from your real Chromium browser are loaded into the headless session for targeted QA testing.

What's the best way to authenticate a headless browser for automated testing?

The best way to authenticate a headless browser is to import cookies from your real Chromium browser. This bypasses manual login workflows by directly loading your existing authenticated session state into the headless environment.

Do I need to manually log in every time I run a headless browser test on an authenticated page?

No, you do not need to manually log in for every headless browser test. By importing cookies from your real Chromium browser into the session, you automatically preserve and apply the login state required for authenticated pages.