setup-browser-cookies

Import authenticated browser cookies into Playwright sessions for QA testing.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/GS-Personal/gstack --skill setup-browser-cookies-gs-personal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/GS-Personal/gstack/tree/main/setup-browser-cookies
Command: npx skills add https://github.com/GS-Personal/gstack --skill setup-browser-cookies-gs-personal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Importing authenticated browser sessions into a headless QA workflow to enable pre-authenticated testing.

Core Features & Use Cases

  • Import cookies from real browsers into a Playwright session for QA testing.
  • Open an interactive cookie picker to select domains to import and load them into the test run.
  • Use before QA testing authenticated pages to accelerate test setup and ensure consistency.

Quick Start

Run the cookie picker to identify and import the domains you need for your QA session, then continue with your test sequence.

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 session for QA testing?

You can import browser cookies into a Playwright session by running an interactive cookie picker to select domains, which then loads the authenticated pages into your headless QA workflow for pre-authenticated testing.

What is pre-authenticated testing and when do I need it for browser test automation?

Pre-authenticated testing is the process of loading valid login sessions into headless browsers before test execution. You need it when QA tests require consistent login states across multiple domains to accelerate test runs.

Can I use this cookie import approach with multiple domains and browsers?

Yes, the cookie picker supports importing authenticated sessions across multiple domains and browsers, ensuring consistent login states throughout your Playwright-loaded QA test runs.

What's the best way to set up authenticated test sessions without logging in during every test run?

The best way is to use a setup workflow that checks your browser binary and uses an interactive cookie picker to import real browser sessions, bypassing repeated login steps and accelerating test setup.

Why does my Playwright test fail to maintain login state across different domains?

Playwright tests fail to maintain login state when cookies are not properly imported. Using an interactive cookie picker to identify and load the required domains ensures consistent pre-authenticated sessions.