skills.rest
GTC6244
GTC6244COMMUNITY
Explore all skills by this author →
GitHub

setup-browser-cookies

Import Chromium browser cookies into headless sessions for authenticated QA testing.

Updated Apr 5, 2026
Search Tags:#browser#headless#import#cookies#chromium#qa-testing#gstack
One-click install
npx skills add https://github.com/GTC6244/ToolBridge --skill setup-browser-cookies-gtc6244
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/GTC6244/ToolBridge/tree/main/.claude/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/GTC6244/ToolBridge --skill setup-browser-cookies-gtc6244

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies into headless browser sessions from your real Chromium browser, enabling authenticated QA tests without manual login.

Core Features & Use Cases

  • Interactive cookie picker to select which domains to import
  • Works before QA testing authenticated pages
  • Supports multiple browsers and domains for testing

Quick Start

Open the cookie picker and select domains to import.

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

You import cookies by using an interactive picker UI to select which authenticated domains from your real Chromium browser to load into the headless browser session, enabling authenticated QA testing without manual login.

What is the best way to test authenticated pages in a headless Chromium environment?▼

The best way to test authenticated pages is to import existing browser cookies from a real Chromium session into the headless environment, using an interactive picker to select specific domains for QA testing.

Can I import cookies from multiple domains into a headless browser session?▼

Yes, you can import cookies from multiple domains into the headless browser session, as the interactive cookie picker supports selecting various domains from your real Chromium browser for testing.

Do I need to manually login to authenticate a headless browser for testing?▼

No, you do not need to manually login to authenticate the headless browser, as you can import cookies from your real Chromium browser to bypass manual authentication for QA testing.

Why are my imported cookies not working in the headless browser session?▼

Imported cookies may not work if the wrong domains were selected, so use the interactive picker UI to ensure you select the correct authenticated domains from your real Chromium browser for the headless session.

Related Skills

Explore More Software Engineering Skills→
florianhornerflorianhorner
4

setup-browser-cookies

Import Chromium browser cookies into a headless browse session.

Community
Advanced
him55710-sudohim55710-sudo

setup-browser-cookies

Import Chromium cookies into a headless browse session for automated QA.

Community
Intermediate
singhianand23045singhianand23045

setup-browser-cookies

Import Chromium cookies into headless browser sessions for authenticated QA testing.

Community
Intermediate
cegit27cegit27
3

setup-browser-cookies

Import authenticated Chromium session cookies into a headless browser session.

Official
Intermediate