skills.rest
zhu637882-stack
zhu637882-stackCOMMUNITY
Explore all skills by this author →
GitHub

setup-browser-cookies

Import Chromium browser cookies into headless sessions for authenticated testing.

1|Updated Apr 6, 2026
Search Tags:#automation#playwright#browser#headless#cookies#qa-testing
One-click install
npx skills add https://github.com/zhu637882-stack/jiaoyi --skill setup-browser-cookies-zhu637882-stack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/zhu637882-stack/jiaoyi/tree/main/qoder-config-backup/skills/gstack-setup-browser-cookies
Command: npx skills add https://github.com/zhu637882-stack/jiaoyi --skill setup-browser-cookies-zhu637882-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the import of cookies from a real Chromium browser into a headless browsing session to enable authenticated test flows.

Core Features & Use Cases

  • Interactive picker UI lets you choose which cookie domains to import, reducing setup friction.
  • Import cookies into the Playwright or similar session to simulate logged-in states across tests.
  • Works before QA on authenticated pages and supports multiple domains for targeted testing.

Quick Start

Plug in your browser cookies using the interactive picker and confirm when ready.

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 session for QA testing?▼

You can import browser cookies into a headless session by using an interactive picker UI to select specific cookie domains, enabling authenticated test flows without manual login steps.

Can I use Playwright to test authenticated pages with my existing browser cookies?▼

Yes, Playwright headless sessions can load cookies from a real Chromium browser, applying them before QA testing to simulate logged-in user contexts across multiple domains.

What is the best way to simulate logged-in states for headless browser automation?▼

Simulating logged-in states for headless browser automation is best done by importing real browser cookies into the session, bypassing the need to script authentication flows for every test run.

Does this cookie import workflow support selecting specific domains?▼

Yes, the cookie import workflow presents an interactive picker UI that lets you choose exactly which cookie domains to import, reducing setup friction when targeting specific authenticated pages.

Why do I need to import cookies for headless QA testing instead of logging in programmatically?▼

Importing cookies for headless QA testing avoids handling complex authentication barriers like multi-factor authentication, directly loading valid logged-in sessions from your Chromium browser into the test environment.

When should I not use browser cookie import for automated testing?▼

You should not use browser cookie import for automated testing when session validity is strictly time-limited or when tests require isolated, fresh authentication states rather than shared real-user cookies.

Related Skills

Explore More Software Engineering Skills→
joeylife94joeylife94

setup-browser-cookies

Import selected cookie domains from Chromium into a headless browser session.

Community
Basic
scanbottscanbott

setup-browser-cookies

Import decrypted Chromium cookies into a Playwright headless test session.

Community
Intermediate
andrew-t-jamesandrew-t-james

setup-browser-cookies

Import browser cookies into a headless session for authenticated testing.

Community
Intermediate
RxFitRxFit

setup-browser-cookies

Import browser cookies into Playwright headless sessions for authenticated page testing.

Community
Intermediate