setup-browser-cookies

Import browser cookies into headless sessions for authenticated QA testing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real Chromium browsers (Comet, Chrome, Arc, Brave, Edge) into the headless browse session to preserve authenticated state during automated QA testing.

Core Features & Use Cases

  • Find the browser binary on your system and open an interactive cookie picker UI that detects installed browsers (Comet, Chrome, Arc, Brave, Edge).
  • Select which cookie domains to import and load them into the headless session for immediate authenticated access.
  • Provide a direct import workflow to skip the UI when a domain is known, followed by verification of the newly imported cookies.

Quick Start

Open the cookie picker, select the domains to import, and verify the imported cookies.

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 automated QA testing?

To import browser cookies for headless QA testing, this Skill locates your installed browser binary, opens an interactive cookie picker UI, and loads selected authenticated domains directly into the headless session while preventing cookie value leakage.

Can I import cookies from Chromium browsers like Chrome, Arc, and Brave into headless automation?

Yes, you can import cookies from Comet, Chrome, Arc, Brave, and Edge. The tool locates the installed browser binary on your system to extract authenticated sessions for headless browsing.

What is the best way to preserve authenticated state across multiple sites in headless QA?

The best way to preserve authenticated state is domain-by-domain cookie selection and reuse. You choose exactly which authenticated domains to import into your headless session for immediate access without repeated manual logins.

Do I need to use the interactive picker UI every time I want to import cookies for testing?

No, you do not need the interactive picker UI every time. When the target domain is already known, you can use a direct import workflow to skip the UI, followed by automatic verification of the newly imported cookies.

Does importing browser cookies into headless automation expose or leak sensitive cookie values?

Importing browser cookies into headless automation is handled safely to avoid leakage of cookie values. The process includes verification of imported cookies while preventing sensitive authentication data from being exposed during automated QA.