skills.rest
pistosmin
pistosminCOMMUNITY
Explore all skills by this author →
GitHub

setup-browser-cookies

Import cookies from Chromium-based browsers into headless sessions for authenticated testing.

Updated Mar 24, 2026
Search Tags:#automation#authentication#playwright#browser#headless#cookie#qa-testing
One-click install
npx skills add https://github.com/pistosmin/base-one --skill setup-browser-cookies-pistosmin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/pistosmin/base-one/tree/main/.claude/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/pistosmin/base-one --skill setup-browser-cookies-pistosmin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real Chromium-based browsers into a headless browse session to preserve authenticated state during automated testing.

Core Features & Use Cases

  • Interactive cookie-domain picker that lets you choose which domains to import for a given test.
  • Supports multiple Chromium-based browsers (Comet, Chrome, Arc, Brave, Edge) for flexible QA workflows.
  • Ensures cookies persist across commands and test runs to enable repeatable automation without manual login.

Quick Start

Run the setup-browser-cookies skill to open the cookie picker and import the domains you need for the current test.

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 automation session?▼

You can import real browser cookies into headless automation by extracting them from Chromium-based browsers and loading them into your test session, preserving authenticated state without manual login for QA workflows.

Can I use cookies from multiple Chromium browsers for automated testing?▼

Yes, automated testing supports importing cookies from multiple Chromium-based browsers including Chrome, Arc, Brave, Edge, and Comet, allowing flexible QA workflows across different local browser profiles.

How does the interactive cookie-domain picker work for test sessions?▼

The interactive cookie-domain picker lets you select specific domains to import for a given test run, ensuring only the necessary authenticated cookies are loaded into the headless browser session.

Do imported browser cookies persist across multiple test runs?▼

Imported browser cookies persist across commands and test runs, enabling repeatable automation without manual login during each execution cycle.

Why do my headless browser tests fail authentication without manual login?▼

Headless browser tests fail authentication because they lack saved session data; importing real browser cookies resolves this by transferring existing authenticated state into the headless environment.

What is the best way to skip login steps in Playwright automation?▼

The best way to skip login steps in Playwright automation is to import cookies from a real Chromium-based browser into the headless session to preserve the authenticated state across test runs.

Related Skills

Explore More Software Engineering Skills→
gth-aigth-ai
1

setup-browser-cookies

Import authenticated session cookies from Chromium browsers into headless Playwright sessions.

Community
Intermediate
SakshamKandelSakshamKandel

setup-browser-cookies

Import Chromium cookies into headless Playwright sessions for authenticated QA testing.

Community
Advanced
westnwestn
1

setup-browser-cookies

Import Chromium browser cookies into a Playwright headless session.

Community
Intermediate
npc-chrisnpc-chris
1

setup-browser-cookies

Import Chromium browser cookies into a headless browser session.

Community
Intermediate