setup-browser-cookies

Name: setup-browser-cookies
Availability: InStock
Author: GenEd

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

Updated Mar 30, 2026

Search Tags:#playwright #qa automation #chromium #browser cookies #session import #authenticated testing

Ready to run

npx skills add https://github.com/GenEducation/GenedUIProject --skill setup-browser-cookies-geneducation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/GenEducation/GenedUIProject/tree/main/.gemini/skills/setup-browser-cookies
Command: npx skills add https://github.com/GenEducation/GenedUIProject --skill setup-browser-cookies-geneducation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill gets your real browser login state into a headless session so you can test authenticated pages without retyping credentials or fighting cookie setup.

Core Features & Use Cases

Browser detection and import picker for Chromium sessions.
Domain-level cookie selection so you only move the sites you need.
Verification step that shows imported cookie counts after the transfer.
Use it before QA runs, bug repros, or any workflow that needs a logged-in state.

Quick Start

Use setup-browser-cookies to import the cookies you need from your Chromium browser before testing the authenticated page.

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

To import browser cookies into a headless Chromium session for QA automation, you select your specific domain interactively, load the decrypted cookies, and verify the imported cookie count to establish an authenticated state. This enables testing authenticated pages without retyping credentials.

Why do I need to import browser cookies for authenticated testing in Playwright?▼

You need to import browser cookies for authenticated testing in Playwright to access real login states in headless sessions. This solves the problem of fighting manual cookie setup or retyping credentials, allowing you to directly test authenticated pages during QA runs or bug repros.

How do I select specific domains when transferring browser cookies for session import?▼

To select specific domains when transferring browser cookies for session import, you use the interactive browser detection and import picker. This domain-level cookie selection ensures you only move the login state for the sites you need into your headless Chromium environment.

Does this cookie import process verify the authenticated state after the transfer?▼

Yes, the cookie import process includes a verification step that shows the imported cookie counts after the transfer. This ensures your decrypted browser cookies were successfully loaded into the headless session before you begin your QA testing or authenticated page checks.

Can I use my existing login state for authenticated page checks without retyping credentials?▼

Yes, you can use your existing login state for authenticated page checks without retyping credentials. By importing your real Chromium browser cookies into the headless session, you replicate the authenticated environment instantly for workflows like bug repros and QA runs.