setup-browser-cookies

Import browser cookies into a Playwright headless session for authenticated QA testing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA engineers often need authenticated access in automated tests. This skill lets you import cookies from your real browser into a headless browse session, avoiding repetitive logins during QA.

Core Features & Use Cases

  • Import cookies from real Chromium-based browsers (Comet, Chrome, Arc, Brave, Edge) into a Playwright headless session.
  • Interactive picker UI to choose which cookie domains to import.
  • Works with direct domain import or the UI for multi-domain cookie provisioning, simplifying authenticated test scenarios.

Quick Start

Open the cookie picker, select the domains to import, then proceed with QA testing.

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

You can import browser cookies for authenticated QA testing by extracting them from real browsers into a Playwright headless session, avoiding repetitive logins during automated test runs.

Can I import cookies from Brave or Edge into a headless browser session?

Yes, you can import cookies from Chromium-based browsers like Brave, Edge, Chrome, Comet, and Arc into a headless browser session to enable authenticated QA testing without manual logins.

How do I select specific cookie domains to import for headless QA testing?

You select specific cookie domains for headless QA testing by using an interactive picker UI, allowing you to choose exactly which domains to import for multi-domain cookie provisioning.

What do I need to run automated browser tests with imported cookies?

To run automated browser tests with imported cookies, you need a browser binary installed on your system, which the skill uses to extract and store cookies for immediate reuse in headless sessions.

Why does my headless QA test keep failing with login prompts despite importing cookies?

Headless QA tests fail with login prompts if you import the wrong cookie domains, but using the interactive picker UI ensures you select the correct domains needed for authenticated access.