setup-browser-cookies

Name: setup-browser-cookies
Availability: InStock
Author: sealion-hub

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

Updated Feb 16, 2026

Search Tags:#playwright #browser #headless #cookies #chromium #qa-testing #cookie-import

Ready to run

npx skills add https://github.com/SeaLion-hub/DICEE --skill setup-browser-cookies-sealion-hub

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/SeaLion-hub/DICEE/tree/main/.agents/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/SeaLion-hub/DICEE --skill setup-browser-cookies-sealion-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps QA engineers run authenticated tests by importing cookies from a real Chromium browser into the headless browsing session.

Core Features & Use Cases

Interactive cookie domain picker to choose which sites to import.
Load selected cookies into the headless browser to simulate logged-in sessions.
Supports multi-domain workflows for local development and CI QA testing.

Quick Start

Open the cookie picker, select the domains to import, and proceed with your QA testing flow.

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

To import real browser cookies into a headless Chromium session for QA testing, use the cookie-import-browser tool with the interactive browser picker UI to securely decrypt and load selected cookies from your local profile.

Can I use Playwright to simulate logged-in sessions across multiple domains?▼

Yes, you can simulate logged-in Playwright sessions across multiple domains by selecting specific sites in the cookie domain picker and loading those decrypted cookies directly into your headless testing environment.

How do I load authenticated states for local development and CI pipelines without manual logins?▼

You can load authenticated states for local development and CI pipelines by importing pre-authenticated cookies from your real Chromium profile into the headless browser session using the cookie-import-browser tool.

Does this QA testing approach require a specific local Chromium profile to decrypt cookies?▼

Yes, this approach requires a local Chromium profile because the cookie-import-browser tool relies on it to securely decrypt and extract the cookies before loading them into the headless browsing session.

What is the best way to authenticate headless browser sessions for QA testing?▼

The best way to authenticate headless browser sessions for QA testing is importing real cookies from your local Chromium profile, which bypasses manual login workflows across multiple domains and environments.

When do I need to import cookies into a headless browser?▼

You need to import cookies into a headless browser when running QA workflows that require pre-authenticated pages across multiple domains, ensuring your testing session simulates a logged-in user state.