setup-browser-cookies

Import browser cookies into a headless session for authenticated testing.

Updated Jul 3, 2025
One-click install
npx skills add https://github.com/andrew-t-james/dotfiles --skill setup-browser-cookies-andrew-t-james
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/andrew-t-james/dotfiles/tree/main/dot_claude/skills/setup-browser-cookies
Command: npx skills add https://github.com/andrew-t-james/dotfiles --skill setup-browser-cookies-andrew-t-james

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real browser into the headless browse session to test authenticated pages without manual login.

Core Features & Use Cases

  • Import cookies from your real browser into a headless session for QA testing.
  • Persist cookies across commands to maintain login state during automated tests.
  • Use when you need to simulate an authenticated user without re-authenticating in every run.

Quick Start

Import cookies from your real browser into the headless session and start testing authenticated pages.

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?

You import browser cookies into a headless session by using interactive Bash prompts to locate your real browser's cookie store and integrate them into the headless browser context. This simulates a logged-in state for QA testing.

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

The best way to test authenticated pages is by importing cookies from a real browser into the headless session. This bypasses manual login, allowing automated tests to simulate an authenticated user context without re-authenticating.

Can I persist login state across automated test runs without re-authenticating?

Yes, you can persist login state across automated test runs by importing real browser cookies into the headless session. This maintains the authenticated user context across commands without requiring manual re-authentication in every run.

Does this cookie import approach work with any specific browser dependencies?

This cookie import approach works independently without external dependencies. It uses Bash with interactive prompts to locate the cookie store from your real browser and integrate cookies directly into the headless browser session.

When do I need to import cookies for headless browser testing?

You need to import cookies when your QA automation or development tests require authenticated access across headless sessions. It allows you to simulate a logged-in user context and test protected pages without performing manual login steps.