skills.rest
antriksh-29
antriksh-29COMMUNITY
Explore all skills by this author →
GitHub

setup-browser-cookies

Import Chromium browser cookies into a headless Playwright session.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real Chromium browser into the headless browse session. This enables authenticated QA flows without manually logging in.

Core Features & Use Cases

  • Interactive cookie picker: Open a UI to select which cookie domains to import.
  • Headless session integration: Loads selected cookies into the Playwright/Headless browser session for immediate use in tests.
  • Pre-QA readiness: Useful before QA testing of authenticated pages or workflows requiring login state.

Quick Start

Open the cookie picker and select the domains to import, then run a test to verify authenticated pages.

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 Playwright headless browser for QA testing?▼

You import cookies into a Playwright headless browser by using an interactive cookie picker UI to select real Chromium browser domains and load them into the session. This enables authenticated QA testing without manual login.

Can I test authenticated pages in headless browser sessions without logging in manually?▼

Yes, you can test authenticated pages by loading real Chromium browser cookies directly into the headless browser session. This bypasses manual login by transferring the existing authenticated state for immediate QA use.

What is the best way to automate QA flows that require an active login state?▼

Automating QA flows requiring a login state is best done by importing cookies from a real Chromium browser into the headless session. This pre-authenticates the browser context, allowing tests to proceed directly to protected scenarios.

Does importing browser cookies work with Chromium domains for headless QA tests?▼

Yes, importing browser cookies works with Chromium domains for headless QA tests. An interactive picker UI allows you to select specific cookie domains from your real browser and inject them into the Playwright session.

How do I select which cookie domains to load into a headless browser session?▼

You select which cookie domains to load by opening the interactive cookie picker UI. From there, you choose the desired authenticated domains from your real Chromium browser to import into the headless session.

Why do my Playwright automated tests fail on authenticated pages in headless mode?▼

Playwright automated tests fail on authenticated pages in headless mode because the session lacks login state. Importing real Chromium browser cookies into the headless session resolves this by providing the required authenticated context.

Related Skills

Explore More Software Engineering Skills→
mattothomasmattothomas

setup-browser-cookies

Import selected Chromium cookie domains into a Playwright headless session.

Community
Intermediate
wormholecowboywormholecowboy
1

agent-browser

Automate browser tasks via CLI with headless Chromium.

Community
Intermediate
PostalocityPostalocity
1

boot-orchestrator

Coordinate framework startup and orchestrate boot sequences across services.

Official
Advanced
CaltexBevoCaltexBevo

setup-browser-cookies

Import Chromium cookies into a Playwright session via an interactive picker.

Community
Advanced