setup-browser-cookies

Import authenticated browser session cookies into a headless Chromium environment.

2|1|Updated May 20, 2026
One-click install
npx skills add https://github.com/balajivis/multiagent-primer --skill setup-browser-cookies-balajivis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/balajivis/multiagent-primer/tree/main/lab0-workflow/gstack/setup-browser-cookies
Command: npx skills add https://github.com/balajivis/multiagent-primer --skill setup-browser-cookies-balajivis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the difficulty of testing authenticated web experiences by importing existing browser login sessions into a headless browsing environment without requiring repeated manual sign-ins.

Core Features & Use Cases

  • Browser Cookie Import: Transfers selected cookie domains from supported Chromium browsers into the headless browse session.
  • Interactive Authentication Setup: Opens a picker workflow for choosing which logged-in domains to import before QA testing.
  • Use Case: Prepare a browser automation session that can access private or authenticated pages for website quality assurance workflows.

Quick Start

Use the setup-browser-cookies skill to import my browser cookies for testing an authenticated website.

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 browser for authenticated testing?

To import browser cookies for authenticated testing, use this Skill to transfer selected cookie domains from supported Chromium browsers into a headless session, bypassing manual sign-ins for private pages.

Can I use Playwright to test private websites without manually logging in each time?

Yes, you can test private websites in Playwright without manual logins by importing your existing authenticated browser session cookies directly into the headless browsing environment.

What is the best way to set up QA testing for authenticated pages across Chromium browsers?

The best way to set up QA testing for authenticated pages is using an interactive picker workflow that detects existing browser cookies, allows domain selection, and securely loads the session for verification.

Does this browser cookie import method work with all headless browsers?

This browser cookie import method applies specifically to Chromium-based browsers, allowing you to extract and load authenticated session cookies for headless browsing and automation workflows.

How do I select which authenticated domains to import before running browser automation?

You select authenticated domains to import through an interactive authentication setup that detects available browser cookies and opens a picker workflow for choosing specific logged-in sessions.

Why do I need session verification when importing cookies for QA testing?

You need session verification when importing cookies for QA testing to confirm that the transferred authenticated browser session is actively valid and properly loaded within the headless environment.