setup-browser-cookies

Import cookies from Chromium-based browsers into headless Playwright sessions.

48|2|Updated Dec 23, 2017

Search Tags:#automation #playwright #browser #headless #cookies #qa-testing #decryption

Ready to run

npx skills add https://github.com/g4rcez/dotfiles --skill setup-browser-cookies-g4rcez

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/g4rcez/dotfiles/tree/main/.ai/skills/setup-browser-cookies
Command: npx skills add https://github.com/g4rcez/dotfiles --skill setup-browser-cookies-g4rcez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates importing cookies from real browsers into a headless Playwright session for authenticated QA testing, eliminating manual sign-in steps.

Core Features & Use Cases

Import cookies from Chromium-based browsers (Chrome/Edge/Arc/Brave/Comet) into headless sessions
Decrypt and load cookies into Playwright for immediate authenticated access
Interactive domain picker to select which domains to import, plus direct-domain import option
Supports session persistence across runs for consistent QA environments

Quick Start

Tell the skill to open the cookie picker, select which domains to import, and load them into your headless browser session.

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

Import browser cookies into a headless Playwright session by using an automation script to decrypt and load cookies from a local Chromium-based browser store, enabling immediate authenticated QA testing without manual sign-in.

Can I use cookies from Chrome or Brave for headless QA testing?▼

Yes, you can use cookies from Chrome, Brave, Arc, Edge, or Comet for headless QA testing. The skill decrypts cookies from any Chromium-based browser store and loads them directly into your Playwright automation runtime.

What's the best way to reproduce a logged-in state across Playwright test environments?▼

The best way to reproduce a logged-in state is importing real browser cookies via an interactive domain picker or direct domain import, decrypting them, and loading them into Playwright to maintain session persistence across test runs.

Do I need a local browser cookie store to set up authenticated headless sessions?▼

Yes, a local Chromium-based browser cookie store is required. You also need a compatible automation runtime and the skill's setup script to decrypt and load the cookies into your headless Playwright session.

How does the interactive domain picker work when importing cookies?▼

The interactive domain picker works by scanning your local browser cookie store, allowing you to select specific domains to import, and then decrypting and loading only those selected cookies into your headless Playwright session.