setup-browser-cookies

Import decrypted browser cookies into a Playwright headless session.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real browser into a headless browse session so authenticated QA flows can be tested without repeated logins.

Core Features & Use Cases

  • Interactive browser cookie import: detect major browsers (Comet, Chrome, Arc, Brave, Edge) and let you pick which domains to import.
  • Per-domain control: choose specific cookie domains to import and apply them to the headless session.
  • Seamless integration: works with the gstack workflow to prepare a ready-to-test browsing environment.

Quick Start

Launch the picker and select domains to import, then confirm to load cookies into your headless 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 browser cookies into Playwright headless tests?

To import browser cookies into Playwright headless tests, use an interactive picker to select specific cookie domains from your real browser. The Skill decrypts and loads these cookies into your headless session, enabling authenticated QA testing without repeated logins.

Can I use cookies from Arc or Brave for Playwright QA testing?

Yes, you can use cookies from Arc or Brave for Playwright QA testing. The Skill detects major browsers including Chrome, Arc, Brave, Edge, and Comet, allowing you to choose which browser's cookie domains to decrypt and import into your headless session.

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

You can test authenticated pages in a headless browser without logging in by importing existing session cookies from your real browser. This allows the headless session to bypass authentication barriers and directly access secured QA flows.

Do I need to manually select cookie domains when importing into a headless session?

Yes, you need to manually select cookie domains when importing into a headless session. The Skill provides an interactive picker that gives you per-domain control, ensuring only the specific authenticated domains you choose are decrypted and applied.

What is the best way to reuse real browser sessions for automated QA testing?

The best way to reuse real browser sessions for automated QA testing is to decrypt and import specific domain cookies into your headless environment. This approach seamlessly integrates with the gstack setup workflow to prepare a ready-to-test browsing state.