skills.rest
stayconnectquick
stayconnectquickCOMMUNITY
Explore all skills by this author →
GitHub

setup-browser-cookies

Import Chromium browser cookies into a Playwright session for authenticated QA testing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real Chromium browser into the headless browse session to enable authenticated QA testing.

Core Features & Use Cases

  • Interactive cookie domain picker to import domains from your real Chromium browser into the Playwright session.
  • Supports selective domain import to simulate logged-in workflows across multiple sites.
  • Verifies loaded cookies and maintains cookie persistence across commands.

Quick Start

Open the cookie picker and select the domains to import, then confirm.

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

You can import real browser cookies into a Playwright session by using an interactive domain picker to select specific Chromium browser domains to load into the headless session.

Can I selectively choose which domains to import for QA testing?▼

Yes, you can selectively choose which domains to import using the interactive cookie domain picker, allowing you to simulate logged-in workflows across multiple sites.

What is the best way to test authenticated workflows in a headless browser?▼

The best way to test authenticated workflows in a headless browser is to import real Chromium browser cookies into the session to bypass login and verify loaded cookies for persistence.

Does this cookie import flow support verifying loaded cookies?▼

Yes, the cookie import flow supports optional verification of loaded cookies and maintains cookie persistence across commands during headless QA testing.

Why do I need to import cookies for headless QA testing?▼

You need to import cookies for headless QA testing to enable authenticated workflows without manual login, allowing you to test logged-in user states across multiple domains.

Are there limitations when importing cookies from a Chromium browser?▼

A limitation is that the cookie import flow requires browser detection of a real Chromium browser and relies on the interactive picker to select domains before loading them into the Playwright session.

Related Skills

Explore More Software Engineering Skills→
thanhtoan105thanhtoan105
1

dev-browser

Automate browser interactions with a persistent Playwright-based Chromium context.

Community
Advanced
DiologIRDiologIR

acceptance-e2e

Automate end-to-end UI tests for web applications using Playwright.

Official
Advanced
SaikeNOSaikeNO

playwright-cli

Automate browser interactions and test web pages with Playwright.

Community
Advanced
burgebjburgebj

setup-browser-cookies

Import cookies from a real Chromium browser into a headless browser session.

Community
Basic