setup-browser-cookies

Import Chromium cookies into a headless Playwright session for QA testing.

1|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/geoffreywoo/clawfable --skill setup-browser-cookies-geoffreywoo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/geoffreywoo/clawfable/tree/main/.claude/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/geoffreywoo/clawfable --skill setup-browser-cookies-geoffreywoo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams and developers need authenticated browser sessions to test sites without logging in each time. This Skill imports cookies from a real Chromium browser into the headless browse session, enabling instant access to authenticated pages for QA.

Core Features & Use Cases

  • Interactive cookie picker UI to select which cookie domains to import.
  • Cookie decryption and loading into the Playwright headless session for immediate use.
  • Supports multiple browsers and shared sessions for team QA workflows.
  • Use Case: QA a site that requires login by importing necessary domain cookies to validate post-login behavior.

Quick Start

Run the on-screen setup to build the browser integration and use the picker to import the domains you need.

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 for QA testing in Playwright?

To import browser cookies for QA testing in Playwright, use an interactive picker UI to select cookie domains, decrypt them, and load them directly into your headless session for authenticated access.

How do I test authenticated pages in a headless browser without logging in?

You can test authenticated pages in a headless browser by importing real Chromium session cookies into your environment, bypassing the need to manually log in during automated QA workflows.

Does the cookie import process require a custom browser build?

Yes, the cookie import process requires a one-time browser build to establish the integration before you can use the picker UI to import domains and decrypt cookies for your session.

Can I select specific cookie domains to load into my headless session?

Yes, you can select specific cookie domains to load into your headless session using the interactive cookie picker UI, allowing targeted QA validation of post-login behavior for required sites.

Why are my imported cookies not working in my headless QA session?

Imported cookies may not work if the one-time browser build was not completed correctly or if the decryption step failed, preventing the domains from loading properly into the Playwright session.