skills.rest
MFS-code
MFS-codeCOMMUNITY
Explore all skills by this author →
Website𝕏@miguelfsernaGitHub

setup-browser-cookies

Import Chromium browser cookies into a headless session with domain selection.

8|2|Updated Mar 24, 2026
Search Tags:#authentication#Playwright#QA testing#Chromium#session setup#headless browsing#browser cookies
One-click install
npx skills add https://github.com/MFS-code/gstack --skill setup-browser-cookies-mfs-code
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/MFS-code/gstack/tree/main/setup-browser-cookies
Command: npx skills add https://github.com/MFS-code/gstack --skill setup-browser-cookies-mfs-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps you reuse an authenticated Chromium session by importing real browser cookies into the headless browse environment, so you can test login-gated pages without re-authenticating every run.

Core Features & Use Cases

  • Interactive cookie domain picker to choose which site domains’ cookies to import.
  • Direct domain import to skip the UI when the user provides a domain (e.g., github.com).
  • Verification summary to confirm which cookie domains were loaded for the session.

Use cases: preparing to QA authenticated pages, importing cookies after the user asks to “import cookies” or “login to the site,” and validating that logged-in browsing works in the headless session.

Quick Start

Invoke /setup-browser-cookies, then select the cookie domains you want to import in the picker UI and tell me when you are done.

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 Playwright headless session?▼

To import real browser cookies into a Playwright headless session, use an interactive cookie picker to select site domains from your real Chromium browser and load them into the test environment for authenticated access.

Why does my QA testing fail on login-protected pages in headless browsing?▼

QA testing fails on login-protected pages in headless browsing because the session lacks authentication. Importing real Chromium browser cookies restores the authenticated state without needing to re-authenticate during every test run.

Can I skip the cookie picker UI and import cookies for a specific domain directly?▼

Yes, you can skip the interactive picker UI by using direct domain import. When you provide a specific domain like github.com, the system imports cookies for that domain directly into the headless browsing session.

How do I verify which authenticated cookie domains are loaded for QA testing?▼

You verify loaded cookie domains using a verification summary. After importing cookies for QA testing, the system confirms which site domains were successfully loaded into the session without exposing the actual cookie values.

Does importing browser cookies for headless browsing expose my sensitive cookie values?▼

No, importing browser cookies for headless browsing does not expose sensitive values. The process includes a verification summary that confirms loaded cookie domains while ensuring the actual cookie data remains hidden.

Related Skills

Explore More Software Engineering Skills→
thanhtoan105thanhtoan105
1

dev-browser

Automate browser interactions with a persistent Playwright-based Chromium context.

Community
Advanced
yocxy2yocxy2

setup-browser-cookies

Imports authenticated Chromium session cookies into headless testing environments.

Community
Intermediate
singhianand23045singhianand23045

setup-browser-cookies

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

Community
Intermediate
mdmagnuson-creatormdmagnuson-creator

auth-headless

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

Community
Advanced