skills.rest
jm199seo
jm199seoCOMMUNITY
Explore all skills by this author →
GitHub

setup-browser-cookies

Import cookies from real browsers into a headless browsing session.

Updated Mar 22, 2026
Search Tags:#automation#browser#headless#cookies#qa-testing#picker
One-click install
npx skills add https://github.com/jm199seo/lostark-accessory-viewer --skill setup-browser-cookies-jm199seo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/jm199seo/lostark-accessory-viewer/tree/main/.claude/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/jm199seo/lostark-accessory-viewer --skill setup-browser-cookies-jm199seo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to import cookies from real browsers into a headless browsing session, enabling authenticated QA and smooth test flows without manual login steps.

Core Features & Use Cases

  • Interactive cookie picker UI to choose which cookie domains to import for a given test session.
  • Browser-detection-based setup that supports Comet, Chrome, Arc, Brave, and Edge, with a one-time or repeatable setup workflow.
  • Works before QA testing of authenticated pages and when you need to simulate a logged-in state across tests.

Quick Start

Open the cookie picker and select which domains to import to the headless session for QA testing of authenticated pages.

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 from Chrome into a headless browser session?▼

You can import cookies from Chrome into a headless browser session using an interactive picker UI to select specific cookie domains for your authenticated QA testing workflows.

Can I use cookies from Arc or Brave for authenticated QA testing?▼

Yes, authenticated QA testing supports importing cookies from Arc, Brave, Comet, and Edge through a browser-detection setup workflow that configures the source browser profiles.

What is the best way to simulate a logged-in state for automated headless testing?▼

Simulating a logged-in state for headless testing is achieved by importing real browser cookies into the session, bypassing manual login steps during QA test execution.

How do I select specific cookie domains to import for a headless test session?▼

You select specific cookie domains to import via an interactive cookie picker UI, allowing you to choose exactly which authenticated domains apply to the current headless session.

Do I need to run a browser setup workflow every time I import cookies?▼

The browser-detection setup workflow is designed to be run one-time or repeatable, detecting Comet, Chrome, Arc, Brave, and Edge profiles before you import cookies into the headless session.

Related Skills

Explore More Software Engineering Skills→
shihwesleyshihwesley

setup-browser-cookies

Import cookies from installed browsers into Playwright sessions for authenticated QA testing.

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
mdmagnuson-creatormdmagnuson-creator

auth-headless

Inject session data into Playwright browser contexts for UI-free authentication.

Community
Advanced