setup-browser-cookies

Imports selected Chromium cookies into headless browser sessions for QA testing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manually setting up cookies in a headless browser can be time-consuming. This skill automates the process, ensuring a consistent testing environment.

Core Features & Use Cases

  • Cookie Import: Imports cookies from your Chromium browser into a headless browser session.
  • Selective Import: Allows users to choose which cookie domains to import.
  • Pre-QA Testing: Useful before performing QA testing on authenticated pages.

Quick Start

To import cookies for 'example.com', run the command: setup-browser-cookies example.com

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 from my browser into a headless browser session for QA testing?

You import cookies into a headless session by selectively transferring them from a Chromium browser based on domain, ensuring a consistent QA testing environment without manual setup.

Can I selectively import cookies for a specific domain into a headless browser?

Yes, you can selectively import cookies into a headless browser by specifying the target domain, which allows you to isolate session data and test only the authenticated pages relevant to your QA workflow.

What is the best way to set up authenticated sessions for headless browser automation?

The best way to set up authenticated sessions for headless browser automation is to import existing cookies directly from a local Chromium browser, bypassing manual login flows and ensuring consistent test environments.

Do I need a specific browser setup to use existing cookies for automated QA testing?

Yes, you need a headless browser setup and your cookies must be stored in a local Chromium browser, as the import process relies on reading session data directly from Chromium's storage to populate the headless environment.

Why does importing browser cookies into a headless session save time during QA testing?

Importing browser cookies into a headless session saves time by automating session setup, eliminating the need to manually authenticate or script login procedures for every test run on protected pages.