setup-browser-cookies

Name: setup-browser-cookies
Availability: InStock
Author: tobiasperry

Import selected cookie domains from Chromium into Playwright headless sessions.

Updated Mar 27, 2026

Search Tags:#playwright #browser #headless #qa-testing #cookie-import #ui-picker

Ready to run

npx skills add https://github.com/TobiasPerry/aws-hackathon --skill setup-browser-cookies-tobiasperry

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/TobiasPerry/aws-hackathon/tree/main/.claude/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/TobiasPerry/aws-hackathon --skill setup-browser-cookies-tobiasperry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real Chromium browser into the headless browse session. Opens an interactive picker UI where you select which cookie domains to import. Use before QA testing authenticated pages. Use when asked to "import cookies", "login to the site", or "authenticate the browser".

Core Features & Use Cases

Import cookies from a real browser into a headless session to preserve login state during automated tests.
Interactive cookie picker that lets you choose which domains to import.
Works with QA workflows that require authenticated pages across environments.

Quick Start

Open the cookie picker, select domains to import, then run your headless tests.

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 from a real browser into a Playwright headless session?▼

To import cookies into a Playwright headless session, use an interactive cookie-domain picker UI to select authenticated domains from your real Chromium browser. This transfers your login state into the headless environment for automated QA testing.

How do I test authenticated pages in headless QA without logging in manually?▼

You can test authenticated pages in headless QA by importing real browser cookies to preserve your login state. An interactive UI lets you select specific cookie domains to transfer before running your automated tests.

Does the cookie import picker require an interactive UI to work?▼

Yes, the cookie import process requires an interactive UI along with bash-based orchestration. You must manually select which cookie domains to import from your real Chromium browser before activating the headless test session.

Can I select specific cookie domains to import for my automated tests?▼

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

What is the best way to authenticate a headless browser for QA testing?▼

The best way to authenticate a headless browser for QA testing is importing real cookies to preserve an authenticated state. This avoids manual login scripts by directly transferring valid session cookies from your Chromium browser.