skills.rest
dogeared
dogearedCOMMUNITY
Explore all skills by this author →
Website𝕏@afitnerdGitHub

setup-browser-cookies

Import Chromium cookies into a headless session via picker UI for authenticated QA flows.

Updated Dec 13, 2017
Search Tags:#automation#qa#setup#playwright#browser#cookies
One-click install
npx skills add https://github.com/dogeared/tnra --skill setup-browser-cookies-dogeared
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/dogeared/tnra/tree/main/.claude/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/dogeared/tnra --skill setup-browser-cookies-dogeared

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real Chromium browser into the headless browse session to enable authenticated QA testing without manual login steps.

Core Features & Use Cases

  • Import cookies from a real browser into your headless session so tests start authenticated.
  • Interactive picker UI lets you select which cookie domains to import for targeted QA.
  • Use during QA testing of sites that require login, or when validating domain-specific session behavior.

Quick Start

Run the gstack setup-browser-cookies skill to import cookies from your real Chromium browser into the headless session and choose which 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 browser cookies into a headless Playwright session?▼

Import browser cookies into a headless session by running the setup-browser-cookies skill, which accesses your local Chromium cookies directory and launches an interactive picker UI to select specific domains for authenticated QA flows.

Can I use my real browser cookies for authenticated QA testing without manual login?▼

You can use real browser cookies for authenticated QA testing without manual login by importing them into your headless session, allowing tests to start already authenticated against sites requiring login.

What do I need to set up browser cookies for headless automation?▼

Setting up browser cookies for headless automation requires a local gstack environment and access to your browser cookies directory, enabling the picker UI to execute and import selected cookie domains.

How do I select specific cookie domains to import for targeted QA testing?▼

Select specific cookie domains for targeted QA testing using the interactive picker UI provided during the import process, letting you choose exactly which domains to bring into the headless browser session.

Does importing browser cookies work for validating domain-specific session behavior?▼

Importing browser cookies works for validating domain-specific session behavior by scoping imported cookies across headless browsers, enabling domain-based cookie testing during QA flows.

Why does cookie import require a local gstack environment?▼

Cookie import requires a local gstack environment because the skill depends on gstack to execute the picker UI and access the local browser cookies directory needed to transfer authentication state into a headless session.

Related Skills

Explore More Software Engineering Skills→
nhattran998nhattran998

setup-browser-cookies

Import cookies from a Chromium browser into a headless session.

Community
Intermediate
wormholecowboywormholecowboy
1

agent-browser

Automate browser tasks via CLI with headless Chromium.

Community
Intermediate
RxFitRxFit

browse

Automate headless browser interactions to verify web pages and test user flows.

Community
Advanced
burgebjburgebj

setup-browser-cookies

Import cookies from a real Chromium browser into a headless browser session.

Community
Basic