setup-browser-cookies

Import Chromium cookies into a Playwright headless browser session.

1|Updated Nov 13, 2025
One-click install
npx skills add https://github.com/concept2cure/ClinicalSageAI-2-replit --skill setup-browser-cookies-concept2cure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/concept2cure/ClinicalSageAI-2-replit/tree/main/.claude/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/concept2cure/ClinicalSageAI-2-replit --skill setup-browser-cookies-concept2cure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps QA testers quickly import cookies from a real Chromium browser into a headless session, preserving authenticated state for automated tests.

Core Features & Use Cases

  • Interactive cookie-domain picker to choose which domains to import
  • Seamless loading of cookies into Playwright or headless browser sessions
  • One-time browser setup validation and guidance for a smooth QA workflow

Quick Start

Run the skill to import cookies 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 real cookies into a Playwright headless browser session?

To import real cookies into a Playwright headless browser session, this skill decrypts cookies from your local Chromium browser and loads them directly into the active context, preserving authenticated state for QA testing.

Can I use my existing Chromium browser cookies for QA testing of authenticated pages?

Yes, you can use your existing Chromium browser cookies for QA testing of authenticated pages. The skill decrypts real cookies from your local browser profile and seamlessly loads them into a headless session, eliminating the need to manually handle login flows in automation scripts.

What is the best way to skip login flows in Playwright automated tests?

The best way to skip login flows in Playwright automated tests is to import real authenticated cookies directly into the headless browser session. This skill allows you to bypass authentication by transferring your active Chromium browser cookies, preserving the logged-in state for QA testing.

Does the cookie import process allow choosing specific domains for headless automation?

Yes, the cookie import process allows choosing specific domains for headless automation by opening an interactive picker. You can select exactly which cookie domains to import from your real Chromium browser, ensuring only the necessary authenticated states are loaded into your Playwright session.

Do I need a specific browser setup to load cookies into a headless session?

You need a real Chromium browser installation with existing authenticated cookies to load cookies into a headless session. The skill includes one-time browser setup validation and guidance to ensure your local environment is correctly configured for a smooth QA workflow.

Why are my authenticated Playwright tests failing to maintain login state?

Authenticated Playwright tests fail to maintain login state when cookies are not properly imported into the headless session. This skill solves that problem by decrypting real Chromium browser cookies and loading them into the active session, preserving the authenticated state for QA testing.