setup-browser-cookies

Import browser cookies into a headless session for authenticated web testing.

127k|19.1k|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/garrytan/gstack --skill setup-browser-cookies
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/garrytan/gstack/tree/main/setup-browser-cookies
Command: npx skills add https://github.com/garrytan/gstack --skill setup-browser-cookies

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of testing authenticated web pages in a headless browser environment by allowing you to import your existing logged-in sessions from your primary browser.

Core Features & Use Cases

  • Seamless Authentication: Import cookies from Chrome, Arc, Brave, Edge, or Comet browsers.
  • Interactive Picker: Visually select which domains' cookies to import.
  • Use Case: Before running automated QA tests on a feature that requires user login, use this skill to import your active session cookies, avoiding manual re-authentication.

Quick Start

Use the setup-browser-cookies skill to import cookies from your browser for the 'example.com' domain.

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

You can import browser cookies into a headless session by leveraging your existing logged-in profiles from Chromium-based browsers. This allows automated QA tests to run against authenticated web pages without requiring manual re-authentication.

Can I sync cookies from Arc, Brave, or Edge browsers for QA automation?

Yes, you can sync cookies for QA automation from multiple Chromium-based browsers including Arc, Brave, Edge, Chrome, and Comet. The skill extracts active session data from these browsers to enable authenticated headless browsing.

What is the best way to test authenticated web pages without logging in manually every time?

The best way to test authenticated web pages without manual login is to import active session cookies from your primary browser into the headless environment. This skips re-authentication by directly leveraging your existing user sessions.

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

You can select specific domains for headless browser automation using an interactive picker. This visually allows you to choose exactly which domains' cookies to import, ensuring only the necessary session data is transferred.

Why do my automated QA tests fail on authenticated pages in headless mode?

Automated QA tests fail on authenticated pages in headless mode because the browser lacks active session credentials. Importing existing browser cookies from an authenticated profile resolves this by providing the required login state.