skills.rest
Bradliebs
BradliebsCOMMUNITY
Explore all skills by this author →
GitHub

setup-browser-cookies

Import Chromium cookies into headless browser sessions for authenticated QA testing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real Chromium browser into the headless browse session, enabling authenticated QA sessions without repeated logins.

Core Features & Use Cases

  • Interactive cookie picker: Open a UI to select which domains to import.
  • Multi-browser support: Works with the real Chrome/Chromium browsers and headless sessions.
  • Secure handling: Decrypts and loads cookies into the Playwright/Headless context without exposing values.
  • Use Case: QA testers can run automated tests against authenticated pages after importing cookies.

Quick Start

Open the cookie picker, select domains to import, and confirm when you are finished.

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 Playwright headless tests?▼

To import cookies from a real Chromium browser, open the interactive cookie picker, select the desired domains to import, and confirm your selection. The tool handles decryption and securely loads the cookies into the headless browse session.

Can I use cookies from my real Chrome browser in a headless QA testing session?▼

Yes, you can use cookies from your real Chrome or Chromium browser in a headless QA testing session. The tool decrypts your existing browser cookies and applies them to the headless context, bypassing frequent login requirements for automated tests.

Why do I need to import cookies for automated testing of authenticated pages?▼

Importing cookies for automated testing is needed when frequent logins are impractical for authenticated pages. Transferring real session cookies to a headless context maintains authentication state securely without repeating manual login workflows during QA testing.

Does importing browser cookies into headless sessions expose sensitive cookie values?▼

Importing browser cookies into headless sessions does not expose sensitive values because the process handles decryption and loading securely. It transfers the authentication state directly into the Playwright context without displaying or exposing the underlying cookie data.

What is the best way to handle authentication for Playwright tests without repeated logins?▼

The best way to handle authentication in Playwright tests without repeated logins is importing real Chromium browser cookies into the headless session. This approach applies existing authenticated sessions to QA tests via a secure cookie decryption and loading process.

Related Skills

Explore More Software Engineering Skills→
mishahaninmishahanin
10

setup-browser-cookies

Import Chromium browser cookies into a JSON store for Playwright automation.

Community
Intermediate
ayubunayubun
8

playwright-debugging

Diagnose and resolve Playwright browser automation test failures, flakiness, and timeouts.

Community
Advanced
whd4whd4

setup-browser-cookies

Import Chromium browser cookies into a Playwright headless session.

Community
Intermediate
atomeamatomeam
2

persistent-browser-sessions

Persist Playwright browser login sessions across automation runs.

Community
Intermediate