skills.rest
lucas-flatwhite
lucas-flatwhiteCOMMUNITY
Explore all skills by this author →
𝕏@lucas_flatwhiteGitHub

setup-browser-cookies

Imports Chromium cookies into a Playwright headless session for authenticated QA testing.

43|7|Updated Mar 13, 2026
Search Tags:#automation#browser#headless#authenticate#qa-testing#cookie-import
One-click install
npx skills add https://github.com/lucas-flatwhite/gstack-ko --skill setup-browser-cookies-lucas-flatwhite
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/lucas-flatwhite/gstack-ko/tree/main/setup-browser-cookies
Command: npx skills add https://github.com/lucas-flatwhite/gstack-ko --skill setup-browser-cookies-lucas-flatwhite

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 and repeatable sessions across environments.

Core Features & Use Cases

  • Interactive cookie picker UI that lets you select which domains to import for the current session.
  • Automatic browser detection and cookie loading into Playwright-based workflows for headless testing.
  • Use before QA testing authenticated pages or when you need to simulate a signed-in user.

Quick Start

Open the cookie picker, select the domains you want to import, and tell me when you're done.

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 for authenticated QA testing?▼

To import cookies for authenticated QA testing, this skill detects your installed Chromium browsers, decrypts the stored cookies, and loads selected domains directly into your headless Playwright session.

Can I use Playwright to test authenticated pages without manually logging in each time?▼

Yes, you can bypass manual login in Playwright by importing cookies from your real Chromium browser into the headless session, enabling repeatable authenticated testing across environments.

How do I select specific domains when importing browser cookies for automation?▼

You can select specific domains for automation using the interactive cookie picker UI, which allows you to manually control exactly which domains are imported before running your QA tests.

Does this cookie import method work with installed Chromium browsers?▼

Yes, this method works by automatically detecting installed Chromium browsers, decrypting their cookie databases, and loading the selected domains into the Playwright workflow.

What is the fallback option if the interactive cookie picker fails to detect domains?▼

If the interactive picker fails or you need a specific domain, you can use the direct-domain import option as a fallback to manually load cookies into the headless browse session.

Why do my headless browser sessions fail to authenticate during QA testing?▼

Headless sessions fail to authenticate because they lack saved login state; importing cookies from your real Chromium browser resolves this by injecting the necessary authentication tokens into the session.

Related Skills

Explore More Software Engineering Skills→
thanhtoan105thanhtoan105
1

dev-browser

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

Community
Advanced
him55710-sudohim55710-sudo

setup-browser-cookies

Import Chromium cookies into a headless browse session for automated QA.

Community
Intermediate
joabgonzalezjoabgonzalez
7

playwright

Automate cross-browser end-to-end testing workflows with Playwright.

Community
Advanced
jerrywu001jerrywu001
6

setup-browser-cookies

Import Chromium session cookies into a headless Playwright browser.

Community
Intermediate