setup-browser-cookies

Import cookies from Chromium-based browsers into a Playwright session.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Vinnni002/Sikshak --skill setup-browser-cookies-vinnni002
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/Vinnni002/Sikshak/tree/main/.claude/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/Vinnni002/Sikshak --skill setup-browser-cookies-vinnni002

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill allows you to import cookies from your actual browser into a headless browsing session, enabling testing of authenticated pages without manual login.

Core Features & Use Cases

  • Browser Cookie Import: Seamlessly transfer cookies from Chromium-based browsers (Comet, Chrome, Arc, Brave, Edge) to a Playwright session.
  • Interactive Domain Selection: An intuitive UI allows you to choose specific domains for cookie import.
  • Use Case: Before conducting QA on a logged-in user's experience, use this Skill to import their active session cookies, ensuring tests reflect real-world authenticated states.

Quick Start

Run the setup-browser-cookies skill to import cookies from your browser.

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 a Playwright headless session?

You can import browser cookies into Playwright by executing a browser-specific import utility that transfers active session data from local Chromium-based browsers into your headless session for authenticated testing.

Can I import cookies from Brave or Arc into a headless browser for testing?

Yes, you can import cookies from Brave, Arc, Chrome, Edge, and Comet by executing the browser-specific import utility to transfer session data directly into your headless browser testing environment.

How do I test authenticated pages in headless browser mode without manual login?

Testing authenticated pages in headless mode without manual login requires importing active session cookies from your local Chromium-based browser into the headless session to maintain the authenticated state.

Is it possible to target specific domains when importing cookies for web testing?

Yes, you can target specific domains when importing cookies for web testing by using the optional direct domain specification feature to retrieve only the session data needed for your authenticated QA tests.

What are the limitations of using imported browser cookies for headless testing?

A limitation of using imported browser cookies for headless testing is that session validity depends entirely on the original browser's active login state, meaning expired local sessions will cause unauthenticated headless tests.