setup-browser-cookies

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

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/akiyoshi/gstack-copilot-jp --skill setup-browser-cookies-akiyoshi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/akiyoshi/gstack-copilot-jp/tree/main/.github/skills/setup-browser-cookies
Command: npx skills add https://github.com/akiyoshi/gstack-copilot-jp --skill setup-browser-cookies-akiyoshi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import logged-in sessions from your Chromium browser into the headless browse session to enable authenticated QA testing across headless environments.

Core Features & Use Cases

  • Cookie import: bring authenticated sessions from Chrome/Edge/Brave into the browse session.
  • Cross-browser support: supports multiple Chromium-based browsers and domain-based cookie selection.
  • Use Case: when you need to test login-protected pages or QA scenarios that require a signed-in state without manual login.

Quick Start

Import cookies from your browser and inject them into the headless browse 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 browser cookies for authenticated Playwright QA testing?

To import browser cookies for authenticated Playwright QA testing, extract logged-in sessions from a real Chromium browser into JSON format and inject them into the headless browse session. This enables testing login-protected pages without manual authentication.

Can I use cookies from Chrome or Brave in a headless browser session?

Yes, you can use cookies from Chrome, Brave, or Edge in a headless browser session. The cookie import process supports multiple Chromium-based browsers, allowing you to transfer authenticated sessions directly into your headless QA environment.

How do I test login-protected pages in headless browsers without manual login?

To test login-protected pages in headless browsers without manual login, export your authenticated session cookies from a local Chromium browser to JSON, then inject them into the headless browse tool to bypass the login flow during QA testing.

Does cookie import support domain-based selection for headless testing?

Yes, cookie import supports optional domain-based selection for headless testing. You can target specific domains when extracting and injecting cookies from your Chromium browser into the headless browse session to ensure precise authenticated QA scenarios.

What is needed to decrypt browser cookies before injecting them into a headless session?

To decrypt browser cookies before injecting them into a headless session, the cookie import process includes optional decryption capabilities. This handles encrypted Chromium cookie data, exporting it to JSON for seamless authenticated QA testing.