skills.rest
SakshamKandel
SakshamKandelCOMMUNITY
Explore all skills by this author →
GitHub

setup-browser-cookies

Import Chromium cookies into headless Playwright sessions for authenticated QA testing.

Updated Apr 24, 2026
Search Tags:#automation#authentication#qa#playwright#browser#headless#cookies
One-click install
npx skills add https://github.com/SakshamKandel/Salt-Route-Consulting- --skill setup-browser-cookies-sakshamkandel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/SakshamKandel/Salt-Route-Consulting-/tree/main/.agents/skills/setup-browser-cookies
Command: npx skills add https://github.com/SakshamKandel/Salt-Route-Consulting- --skill setup-browser-cookies-sakshamkandel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real Chromium browser into the headless browse session to enable authenticated QA testing across domains without manual login.

Core Features & Use Cases

  • Import cookies from local Chromium profiles into headless browser sessions to preserve login state across tests.
  • Open a cookie picker to select which domains to import and manage sessions.
  • Support direct domain import or interactive selection for authenticated testing across multiple sites.

Quick Start

Tell me which domains to import, then confirm to load cookies 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 cookies into a Playwright headless browser session?▼

To import cookies into Playwright headless sessions, you use a cookie-import workflow to decrypt and load cookies from your local Chromium browser profile, enabling authenticated QA testing without requiring manual logins for each test run.

Can I preserve login state for cross-domain testing without manual authentication?▼

Yes, you can preserve login state for cross-domain testing by importing real browser cookies into headless sessions, allowing automated QA scripts to bypass authentication flows and maintain persistent authenticated states across multiple domains.

How do I select specific domains when importing browser cookies for automation?▼

You can select specific domains during cookie import by using an interactive domain picker, or by providing direct domain inputs, allowing you to load only the necessary session cookies for targeted authenticated testing across selected sites.

Do I need a specific browser setup to decrypt and load cookies for headless QA testing?▼

You need a local Chromium browser profile and a Playwright-based headless session to decrypt and load cookies, as the workflow relies on extracting existing authentication data from your active browser to inject into the automated environment.

Why are my headless browser tests failing to maintain authenticated sessions across domains?▼

Headless tests fail to maintain authenticated sessions across domains when cookies are not imported properly, requiring a dedicated workflow to decrypt local Chromium profiles and inject the active session cookies into the headless context before executing tests.

Related Skills

Explore More Software Engineering Skills→
mishahaninmishahanin
10

setup-browser-cookies

Import Chromium browser cookies into a JSON store for Playwright automation.

Community
Intermediate
Svenja-devSvenja-dev
38

e2e-testing

Automate end-to-end browser testing for web applications with Playwright MCP.

Community
Intermediate
wormholecowboywormholecowboy
1

agent-browser

Automate browser tasks via CLI with headless Chromium.

Community
Intermediate
ManzuetiManzueti

setup-browser-cookies

Import cookies from a Chromium browser into a headless browser session.

Community
Basic