skills.rest
mulyoved
mulyovedCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

setup-browser-cookies

Import Chromium browser cookies into headless sessions for authenticated QA testing.

Updated Mar 30, 2026
Search Tags:#automation#authentication#browser#headless#cookies#qa-testing
One-click install
npx skills add https://github.com/mulyoved/awesome-agent-ides --skill setup-browser-cookies-mulyoved
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/mulyoved/awesome-agent-ides/tree/main/.agents/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/mulyoved/awesome-agent-ides --skill setup-browser-cookies-mulyoved

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When QA testing authenticated pages, cookies from real browsers are required to preserve login state across headless sessions. This Skill provides a reliable way to import cookies into the headless browser session so tests can run without repeated logins.

Core Features & Use Cases

  • Interactive picker: opens a UI to select which cookie domains to import.
  • Session persistence: loads and persists cookies in the headless session for subsequent commands.
  • Pre-QA setup: enables testing authenticated pages before manual QA or automated tests.

Quick Start

Open the cookie picker and select which domains to import for your QA sessions.

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 can import browser cookies into a headless session by using an interactive picker to select cookie domains, which then handles decryption and loads them for authenticated QA testing.

Can I carry over real Chromium browser login cookies to automated tests?▼

Yes, you can carry over real Chromium browser login cookies to automated tests by importing them into the headless session, preserving your authentication state across commands without repeated logins.

How do I select specific cookie domains to import for my headless browser?▼

You select specific cookie domains by using the browser-based interactive picker UI, which opens to let you choose which authenticated domains to load into the headless session.

Do my imported session cookies persist across different commands and automated tests?▼

Yes, imported session cookies persist across different commands and automated tests, loading and maintaining the authenticated state in the headless session for subsequent executions.

Why do my headless browser tests fail on pages that require login?▼

Headless browser tests fail on login pages because they lack authenticated session cookies, which you can resolve by importing real browser cookies to preserve login state across sessions.

Related Skills

Explore More Software Engineering Skills→
hetsheth-droidhetsheth-droid

setup-browser-cookies

Import selected Chromium cookies into a Playwright headless session.

Community
Intermediate
him55710-sudohim55710-sudo

setup-browser-cookies

Import Chromium cookies into a headless browse session for automated QA.

Community
Intermediate
singhianand23045singhianand23045

setup-browser-cookies

Import Chromium cookies into headless browser sessions for authenticated QA testing.

Community
Intermediate
gaaschkgaaschk

setup-browser-cookies

Import cookies from real browsers into headless sessions via an interactive picker.

Community
Advanced