get-cookies

Import logged-in browser cookies into Playwright automation sessions.

3|1|Updated Mar 17, 2026

Search Tags:#authentication #playwright #browser-automation #cookies #qa-testing #session-import

Ready to run

npx skills add https://github.com/cogine-ai/cogine-dev-skillset --skill get-cookies

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: get-cookies
Source: https://github.com/cogine-ai/cogine-dev-skillset/tree/main/skills/get-cookies
Command: npx skills add https://github.com/cogine-ai/cogine-dev-skillset --skill get-cookies

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps QA engineers reuse authenticated browser sessions by importing cookies from a real browser into a local automation session, enabling tests against protected pages without manual logins.

Core Features & Use Cases

Import cookies from a real Chromium-based browser into your Playwright/Test automation session.
Selectively enable domains, manage per-domain cookies, and reuse sessions across test steps.
Ensure cookies persist between commands and verify the authenticated state before tests run.

Quick Start

Run the cookie-import-browser tool to load your browser cookies for your Playwright session, then continue testing.

Frequently Asked Questions about get-cookies

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I import real-browser cookies into a Playwright session?▼

To import cookies into Playwright, run the cookie-import-browser helper to discover installed Chromium-based browsers, select target domains, decrypt cookies, and load them into your active automation session.

Can I reuse an authenticated browser session for automated QA testing?▼

Yes, you can reuse an authenticated browser session by importing logged-in cookies from a real browser into your local automation session, enabling tests against protected pages without manual logins.

Does cookie import work with all browsers or only Chromium-based ones?▼

Cookie import targets Chromium-based browsers specifically. The browser helper discovers installed browsers to decrypt and load their cookies into your local Playwright automation session.

What is the best way to test protected pages without logging in manually every time?▼

The best way is importing real-browser cookies into your automation session. This persists authenticated sessions between commands, verifying the logged-in state before tests run.

Can I selectively choose which domains to import cookies for during browser automation?▼

Yes, the cookie import process allows selectively enabling domains and managing per-domain cookies, so you can control exactly which authenticated sessions load into your Playwright test.

Why do my imported cookies not persist between Playwright test steps?▼

Imported cookies should persist between commands when properly loaded. Use the browser helper to verify the authenticated state before tests run, ensuring sessions remain active across test steps.