setup-browser-cookies

Import decrypted Chromium cookies into a Playwright headless session.

Updated May 11, 2026
One-click install
npx skills add https://github.com/wodeh/gstack-kimi --skill setup-browser-cookies-wodeh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/wodeh/gstack-kimi/tree/main/setup-browser-cookies
Command: npx skills add https://github.com/wodeh/gstack-kimi --skill setup-browser-cookies-wodeh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from a real Chromium browser into a headless session to enable authenticated testing without repeated logins.

Core Features & Use Cases

  • Interactive cookie picker to select domains to import.
  • Seamless loading of decrypted cookies into the headless browser session.
  • Useful for QA workflows that require authenticated access to test sites.

Quick Start

Run the setup-browser-cookies skill and follow the interactive picker to import your domains.

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

To import real-browser cookies into a Playwright headless session, use an interactive cookie picker UI to select domains, which decrypts the cookies and loads them directly into your automated test environment.

Can I test authenticated pages with Playwright without performing repeated logins?

Yes, you can test authenticated pages without repeated logins by importing existing cookies from a real Chromium browser into the headless session, bypassing the login flow during QA testing.

Does the setup-browser-cookies skill work with Chromium browser profiles?

Yes, it works with Chromium browser profiles by extracting and decrypting cookies directly from your local browser data, allowing you to select specific domains via an interactive picker.

How do I select specific domains when importing cookies for automated workflows?

You select specific domains for automated workflows using an interactive cookie picker UI that appears when you run the skill, letting you choose exactly which authenticated site cookies to decrypt and load.

What is the best way to handle authenticated access for QA testing in headless browsers?

The best way to handle authenticated access for QA testing in headless browsers is importing decrypted cookies from a real Chromium browser session, enabling immediate authenticated access without automating login forms.