setup-browser-cookies

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

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ingoatl/propertycentral --skill setup-browser-cookies-ingoatl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/ingoatl/propertycentral/tree/main/.claude/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/ingoatl/propertycentral --skill setup-browser-cookies-ingoatl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real Chromium browser into a headless browse session to enable authenticated QA flows without manual login steps.

Core Features & Use Cases

  • Interactive cookie picker that lets you select which domains to import.
  • Pre-authenticated headless sessions for QA on pages requiring login.
  • Supports multiple browsers and environments via a single, repeatable setup.

Quick Start

Run the setup-browser-cookies skill to import cookies from your real Chromium browser into the headless session.

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 cookies into a headless browser for authenticated QA testing?

You import cookies into a headless browser by running the setup-browser-cookies skill, which extracts them from a real Chromium browser session and applies them to your headless environment. This enables pre-authenticated QA flows without manual login steps.

Can I choose which cookie domains to import for my headless session?

Yes, you can choose which cookie domains to import using the interactive cookie picker provided by the skill. This allows you to selectively import authentication data for specific domains before executing your QA scripts.

Does this cookie import method work with Chromium-based headless environments?

Yes, this method works with Chromium-based headless environments by directly importing cookies from a real Chromium browser. It supports pre-authenticated sessions for QA on pages that require login across multiple browsers via a repeatable setup.

What is the best way to skip manual login steps in headless browser QA?

The best way to skip manual login steps in headless browser QA is to import real cookies from an authenticated Chromium session. This provides a pre-authenticated state for your headless session, allowing script-driven operations to immediately access protected pages.

Do I need a real browser installed to import cookies for headless testing?

Yes, you need a real Chromium browser installed because the skill extracts existing cookies from that browser's profile. It uses internal tooling to pull the authentication data and apply it to the headless session before running your QA tests.