setup-browser-cookies

Import Chromium browser cookies into a headless session for authenticated testing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real Chromium browser into the headless browse session to enable authenticated test flows.

Core Features & Use Cases

  • Import cookies from a real browser into a headless session to preserve login state for QA and automation.
  • Use before QA testing of authenticated pages to ensure consistent sessions across tests.
  • Interactive picker UI lets you select which cookie domains to import.

Quick Start

Trigger /setup-browser-cookies to open the cookie picker and import the domains you need.

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?

To import cookies for QA testing, trigger /setup-browser-cookies to open an interactive picker UI that transfers cookies from your real Chromium browser into a headless session, preserving login state for automated workflows.

What is the best way to test authenticated pages in a headless browser?

Testing authenticated pages in a headless browser requires importing existing login cookies from your Chromium browser session. This skill provides an interactive domain picker UI to select and transfer the exact session cookies needed.

Can I use my existing Chromium login state for headless browser automation?

Yes, you can use your existing Chromium login state for headless automation by importing specific cookie domains. The interactive picker UI lets you select which authenticated domains to transfer into the headless session.

How do I select which cookie domains to import for cross-domain session testing?

Selecting cookie domains for cross-domain session testing is handled by an interactive UI. When you trigger the workflow, the picker prompts you to choose specific domains from your real browser cookies to import into the headless session.

Do I need any external dependencies to set up browser cookies for headless testing?

No external dependencies are required to set up browser cookies. The workflow is implemented as a Bash-based process using standard Read and AskUserQuestion tools, with optional scripts and assets controlled by SKILL.md.