setup-browser-cookies

Import cookies from Chrome, Arc, Brave, Edge, and Comet into Playwright sessions.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/TimHL5/carousel --skill setup-browser-cookies-timhl5
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/TimHL5/carousel/tree/main/.claude/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/TimHL5/carousel --skill setup-browser-cookies-timhl5

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Headless QA testing often requires pre-authenticated sessions; this skill imports cookies from real browsers into the headless run so tests can start on authenticated pages without manual login.

Core Features & Use Cases

  • Import cookies from Comet, Chrome, Arc, Brave, and Edge into the headless session.
  • Open an interactive cookie picker UI to select which domains to import.
  • Use pre-authenticated cookies to quickly test logged-in flows in automated QA.

Quick Start

Run the setup-browser-cookies skill and use the picker to import the domains you want to test, then confirm when done.

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 sessions?

You can import real browser cookies into Playwright headless sessions by running a one-time setup script in the skill directory, then using an interactive picker to select which domains to load before starting authenticated tests.

Can I use cookies from Chrome, Arc, Brave, and Edge for headless QA testing?

Yes, headless QA testing supports importing cookies from Chrome, Arc, Brave, Edge, and Comet. You use the interactive picker to choose specific domains and load them into the session to bypass manual login.

How do I run authenticated Playwright tests without manual login?

To run authenticated Playwright tests without manual login, import pre-authenticated cookies from your real browser into the headless session. The loaded cookies let tests start directly on logged-in pages.

What's the best way to skip login flows in automated QA testing?

The best way to skip login flows in automated QA testing is importing existing browser cookies into the headless environment. This allows tests to launch on authenticated pages immediately without entering credentials.

Do I need a setup script before importing browser cookies for testing?

Yes, you need to run a one-time setup script in the skill directory before importing browser cookies. After setup, use the interactive cookie picker to select domains and confirm them for your headless session.

Why do my headless tests fail on authenticated pages?

Headless tests fail on authenticated pages because the session lacks valid login credentials. Importing real browser cookies into the headless run loads the pre-authenticated state required to access logged-in flows.