gstack-setup-browser-cookies

Import Chromium cookies into a headless browse session via interactive picker.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/AlexandreLab/dotfiles --skill gstack-setup-browser-cookies-alexandrelab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack-setup-browser-cookies
Source: https://github.com/AlexandreLab/dotfiles/tree/main/claude/skills/gstack-setup-browser-cookies
Command: npx skills add https://github.com/AlexandreLab/dotfiles --skill gstack-setup-browser-cookies-alexandrelab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines authenticated testing by importing cookies from a real Chromium browser into a headless session, eliminating the need for repeated logins during automation.

Core Features & Use Cases

  • Interactive cookie picker: choose which domains to import into the headless session.
  • Maintains login state for QA, automation, and test runs across multiple domains.

Quick Start

Launch the interactive picker, select the domains you want, and confirm to import cookies.

Frequently Asked Questions about gstack-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 a headless session?

To import real browser cookies into a headless session, this skill reads existing Chromium authentication data, provides an interactive picker UI to select specific domains, and loads those cookies into the automated browser context.

Can I maintain login state for QA testing without repeated logins?

Yes, you can maintain login state for QA testing without repeated logins by importing existing authenticated cookies from a real Chromium browser directly into your headless session, preserving the active authentication context.

Does this cookie import tool work with Chromium browsers?

Yes, this cookie import tool works specifically with Chromium browsers by extracting existing authenticated session cookies and transferring them into a headless browsing environment for automated workflows.

How do I select which domains to import when switching between authenticated pages?

To select which domains to import when switching between authenticated pages, launch the interactive picker UI, choose the specific cookie domains needed for your workflow, and confirm the transfer into the headless session.

What is the best way to automate authenticated testing across multiple domains?

The best way to automate authenticated testing across multiple domains is importing real browser cookies into a headless session via an interactive picker, eliminating manual re-authentication during automated test runs.