setup-browser-cookies

Import cookies from a Chromium browser into a headless session.

15|1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/howdeploy/NekoFree --skill setup-browser-cookies-howdeploy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/howdeploy/NekoFree/tree/main/skills/setup-browser-cookies
Command: npx skills add https://github.com/howdeploy/NekoFree --skill setup-browser-cookies-howdeploy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real Chromium browser into the headless browse session.

Core Features & Use Cases

  • Interactive picker UI to select which cookie domains to import
  • Load cookies into the headless browse session to enable authenticated testing
  • Use before QA testing authenticated pages or when asked to "import cookies" or "authenticate the browser"

Quick Start

Open the cookie picker and import the selected domains into the headless browser session.

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 session for QA testing?

To import browser cookies into a headless session, use a tool that reads cookies from your real Chromium browser, decrypts them if needed, and loads them into the headless session to enable authenticated QA testing of protected pages.

Can I reuse my real Chromium login state for headless automation?

Yes, you can reuse your real Chromium login state for headless automation by importing and decrypting existing browser cookies to load your active authentication session directly into the headless environment.

What is the best way to authenticate a headless browser without handling login forms?

The best way to authenticate a headless browser without handling login forms is to import cookies from your real Chromium browser, allowing you to bypass authentication and directly access authenticated pages for testing.

How do I select specific cookie domains to load into my automation session?

You can select specific cookie domains to load into your automation session using an interactive picker UI, which allows you to choose exactly which authenticated domains are imported into the headless browser.

Why do my imported browser cookies need to be decrypted for headless testing?

Imported browser cookies need to be decrypted for headless testing because Chromium encrypts sensitive cookie data locally, requiring decryption before the headless session can read and apply the authentication state.