setup-browser-cookies

Import Chromium browser cookies into a headless Playwright session.

Updated Dec 22, 2019
One-click install
npx skills add https://github.com/sajalsuhane/sajalsuhane.github.io --skill setup-browser-cookies-sajalsuhane
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/sajalsuhane/sajalsuhane.github.io/tree/main/.claude/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/sajalsuhane/sajalsuhane.github.io --skill setup-browser-cookies-sajalsuhane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import and load cookies from a real Chromium browser into a headless browse session to enable authenticated QA without manual login.

Core Features & Use Cases

  • Interactive cookie-domain picker to select which domains to import into the headless session.
  • Supports one-time setup and loading of session cookies for QA testing of authenticated pages.
  • Works with Playwright-based workflows that reuse cookies across commands.

Quick Start

Use the cookie picker to import domains from your Chromium profile into the 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 real browser cookies into headless test sessions?

You can import real browser cookies into headless test sessions by using an interactive picker UI to select domains from your Chromium profile and load them directly into the headless environment. This simulates a logged-in state for QA testing.

Can I use imported cookies to test authenticated pages without manual login?

Yes, loading imported cookies into a headless session simulates an authenticated state, allowing you to test authenticated pages without performing manual login. This enables one-time setup for QA testing of protected routes.

Does the cookie import picker work with Playwright workflows?

The cookie import picker works with Playwright-based workflows by reusing loaded session cookies across commands. It requires a Bash-based environment to run the interactive domain selection UI for the headless session.

What is the best way to set up session cookies for QA testing of authenticated pages?

The best way to set up session cookies for QA testing is using an interactive cookie-domain picker that imports them from a real Chromium browser profile. This simulates a logged-in state directly in the headless testing session.

Do I need a specific environment to load Chromium cookies into a headless browser?

You need a Bash-based environment to run the interactive picker UI that selects domains and loads cookies into the headless session. The process imports existing session data from a real Chromium browser profile.