setup-browser-cookies

Name: setup-browser-cookies
Availability: InStock
Author: yocxy2

Imports authenticated Chromium session cookies into headless testing environments.

Updated Jul 26, 2026

Search Tags:#automation #testing #authentication #qa #browser #cookies

Ready to run

npx skills add https://github.com/yocxy2/gstack3 --skill setup-browser-cookies-yocxy2

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/yocxy2/gstack3/tree/main/setup-browser-cookies
Command: npx skills add https://github.com/yocxy2/gstack3 --skill setup-browser-cookies-yocxy2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the friction of manually logging into test environments by importing your existing, authenticated browser cookies directly into the headless testing session.

Core Features & Use Cases

Automated Authentication: Securely transfers session cookies from your local Chromium browser to the headless environment.
Interactive Selection: Provides a visual picker to choose specific domains for import, ensuring only necessary credentials are used.
Use Case: When you need to run automated QA tests on a site that requires a login, use this skill to bypass the manual login flow and start testing immediately with your active session.

Quick Start

Invoke the setup-browser-cookies skill to import your authenticated session cookies for the current site.

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 authenticated browser cookies into a headless testing environment?▼

To import authenticated browser cookies into a headless testing environment, this skill securely transfers your local Chromium session cookies directly into the testing session, bypassing manual login flows for automated QA.

Why does my automated QA test fail on protected web pages?▼

Automated QA tests often fail on protected web pages because headless environments lack active session cookies. Transferring authenticated cookies from your local browser provides the necessary login state to test these pages immediately.

What is the best way to bypass manual login for end-to-end testing?▼

The best way to bypass manual login for end-to-end testing is to inject existing authenticated session cookies from your local Chromium browser into the headless environment, eliminating login friction and starting tests immediately.

Does this cookie injection approach work with any browser besides Chromium?▼

No, this cookie injection approach currently requires access to local Chromium browser cookie stores. It uses a specific binary to perform secure decryption and injection for QA testing environments.

How do I select specific domains for cookie import during automated testing?▼

To select specific domains for cookie import during automated testing, you can use the interactive visual picker provided by the skill, ensuring only the necessary credentials for your target site are transferred.

Do I need a specific binary to decrypt local browser cookies for QA?▼

Yes, you need the gstack browse binary to perform secure decryption and injection of local browser cookies into the headless testing environment for your automated QA workflows.