setup-browser-cookies

Import Chromium cookies into headless browser sessions for automated testing.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/greencm/gstuck --skill setup-browser-cookies-greencm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/greencm/gstuck/tree/main/output/gstack/setup-browser-cookies
Command: npx skills add https://github.com/greencm/gstuck --skill setup-browser-cookies-greencm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill allows for importing cookies from your regular Chromium browser into a headless browser session, enabling authentication and personalized browsing within automated tests and workflows.

Core Features & Use Cases

  • Cookie Import: Transfer cookies across sessions between the real browser and the headless browser.
  • Authentication Support: Facilitate authenticated access to sites within automated tests and QA processes.
  • Use Case: Before conducting automated tests on a site requiring authentication, import the necessary cookies from your real browser to ensure seamless login and interaction.

Quick Start

Run the 'setup-browser-cookies' skill to import cookies into your headless browsing 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 real browser cookies into a headless browser session?

Cookie migration transfers authentication cookies from your regular Chromium browser into a headless browser session, enabling authenticated access to web applications during automated QA testing.

Can I use imported browser cookies for authenticated automated testing?

Yes, imported browser cookies support authenticated automated testing by allowing headless browsing sessions to use real user login states, bypassing the need to script manual authentication flows for QA processes.

Do I need a headless browser to use imported cookies for automated QA?

Yes, you need headless browser capabilities because this Skill ensures compatibility with headless browsing sessions specifically for automated test execution and QA workflows requiring authenticated access.

What's the best way to authenticate a headless browser without logging in manually?

Transferring cookies from a real browser session to the headless environment is the best way to authenticate automatically, ensuring seamless login and interaction during automated tests without manual input.

Why does my headless browser test fail on authenticated web pages?

Headless browser tests fail on authenticated pages when session cookies are missing; importing real browser cookies into the headless session resolves this by providing the necessary authentication state.