setup-browser-cookies

Name: setup-browser-cookies
Availability: InStock
Author: him55710-sudo

Import Chromium cookies into a headless browse session for automated QA.

Updated Mar 19, 2026

Search Tags:#authentication #playwright #browser #headless #chromium #qa-testing #cookie-import

Ready to run

npx skills add https://github.com/him55710-sudo/uni-foli --skill setup-browser-cookies-him55710-sudo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/him55710-sudo/uni-foli/tree/main/.agents/skills/gstack-setup-browser-cookies
Command: npx skills add https://github.com/him55710-sudo/uni-foli --skill setup-browser-cookies-him55710-sudo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real Chromium browser into the headless browse session to preserve login state during automated QA. Without cookies, tests may fail on authenticated pages and require repeated logins.

Core Features & Use Cases

Import cookies from your real browser into the headless session to maintain authentication during automated QA.
Interactive picker UI lets you choose which cookie domains to import.
Use before QA testing authenticated pages to speed up test iterations.

Quick Start

Open the cookie importer, select the domains you want to import, and start the headless test 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 for headless QA testing?▼

To import browser cookies for headless QA testing, you can use an interactive picker to select specific cookie domains from your real Chromium browser and load them into the headless session to preserve login state.

Why do my Playwright authentication tests fail in headless browser sessions?▼

Playwright authentication tests fail in headless browser sessions because they lack login state. Importing cookies from your real Chromium browser preserves authentication and prevents repeated logins during automated QA.

Can I choose which cookie domains to import for my automated QA session?▼

Yes, you can choose which cookie domains to import for your automated QA session. The cookie importer provides an interactive picker UI to select specific domains before initializing the headless test session.

What's the best way to maintain login state across headless Chromium test iterations?▼

The best way to maintain login state across headless Chromium test iterations is importing cookies from your real browser. This preserves authentication during automated QA and speeds up testing on authenticated pages.

Does importing browser cookies into a headless session require repeated logins?▼

No, importing browser cookies into a headless session does not require repeated logins. By loading cookies from your real Chromium browser, you preserve the authentication state needed for testing authenticated pages.