Skip to content

Guide · Agent skill

How to use the Invisible Playwright Browser Identities agent skill

Updated · written with AI from the project's own documentation and checked against our catalogue data

The invisible-playwright skill teaches an AI agent to use managed browser identities: separate Firefox profiles, each with its own cookies, logins and browser fingerprint, that websites see as a person at a computer. This guide explains what the skill does, how to install it, how to ask for it in plain language, and the safety points to check before you rely on it. By the end you will know how to install the skill, how the agent opens and closes an identity, and when a plain download is the better choice.

Invisible Playwright Browser Identitiesfeder-cr/invisible_dots · MIT

Quick start

  1. 1Download the ZIP. Get the invisible-playwright ZIP from this page. It contains the SKILL.md file.
  2. 2Unzip the skill. Unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder.
  3. 3Or upload it in the Claude apps. Open Settings → Capabilities → Skills and upload the ZIP.
  4. 4Confirm the requirements. Make sure the invisible_dots runtime, the invisible_playwright browser server, Firefox and a local desktop are available.
  5. 5Ask for a website task. Describe the task and name the account, for example a personal or work login, so the agent picks the right identity.
  6. 6Review the result and close the identity. Check what the agent did. The agent should close the identity once the task is done, though you can ask it to confirm.

What the skill makes the agent do

Agent skills are instruction files that give an AI agent extra know-how for a specific kind of task. This one covers the browser identities: which identity to use, how to open and close one, and when to skip the browser altogether.

A browser identity is one person on the web. Its profile, cookies, logins and fingerprint are kept on disk between uses, so the same identity can come back logged in to a site the next time.

  • The agent can list identities, see which are open, and check how many may be open at once.
  • It can create a new identity, which starts closed, and launch or close an existing one.
  • It reuses an identity that is already logged in to a site instead of making a new one.
  • It keeps one identity per person or account it acts as.
  • It uses a separate identity when one task must not touch another, such as checking a mailbox during a sign-up.

Install the invisible-playwright skill

You can install the skill in two ways. Download the ZIP from this page first. The skill is a single file named SKILL.md.

For a personal setup, unzip the download into ~/.claude/skills/. To limit it to one project, unzip it into that project's .claude/skills/ folder. In the Claude apps you can instead upload the ZIP under Settings → Capabilities → Skills.

  • Personal: unzip into ~/.claude/skills/
  • Single project: unzip into the project's .claude/skills/ folder
  • Claude apps: Settings → Capabilities → Skills, then upload the ZIP

Check what the skill needs before you start

The skill depends on the invisible_dots runtime with the invisible_playwright browser server, and on Firefox managed by that server. The browser has to open on a local desktop environment, so the agent needs a desktop to show it on.

The skill runs scripts and uses the network. Plan for that before you install it on a machine that holds sensitive data.

  • invisible_dots runtime with the invisible_playwright browser server
  • Firefox managed by that server
  • A local desktop environment for the browser to open on

Trigger the skill with natural requests

You do not need a special command. Describe a task that involves a website or a web search, and the agent will decide whether the browser identities are needed. Name the account when it matters, so the agent picks the right identity.

If a plain download or API call will do the job, the agent should use curl instead of opening a browser. You can ask for that directly.

  • Check my bank statement page for last month's total, using my personal account.
  • Log in to the supplier portal with my work account and download the latest order list.
  • Search the web for the current opening hours of this museum and summarise them.
  • Download this CSV file directly; no browser needed.

Know how identities are opened, closed and kept

Opening an identity puts a real Firefox window on your desktop. The first launch of a new identity can take minutes. Closing an identity keeps its profile, cookies and logins, so the next launch can pick up where it left off.

The agent should close an identity once the task no longer needs it, because an open browser uses memory on your computer. Each page action targets the identity that is open, and it acts on that identity's one page.

  • browser_identity_list shows identities, which are open, and the open limit.
  • browser_identity_create makes an identity, closed, from a name.
  • browser_identity_launch opens an identity on your desktop.
  • browser_identity_close closes it; profile, cookies and logins stay on disk.
  • Page tools take the identity_id of an open identity.

Save notes on repeated site tasks

When the agent works out how to do something on a site it will repeat, such as where the login sits or which steps a form needs, it can save those notes as its own small skill. Each one is a SKILL.md file in /home/dot/skills/ under a folder named for the task.

Review these notes before you rely on them. They record how a site worked at one point and may need updating when the site changes.

What people use it for

  • Logging in to a site with one account and downloading a report from inside the logged-in session.
  • Keeping a personal and a work account on the same website in separate identities so they do not mix.
  • Signing up to a service in one identity while reading a verification email in a second, throwaway-mail identity.
  • Researching pages that have no plain API by browsing them like a person would.
  • Choosing curl for a direct file download so no browser is opened at all.

Frequently asked questions

How do I install the invisible-playwright skill?

Download the ZIP from this page and unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder. In the Claude apps, upload the ZIP under Settings → Capabilities → Skills.

What does the invisible-playwright skill need to run?

It needs the invisible_dots runtime with the invisible_playwright browser server, Firefox managed by that server, and a local desktop environment for the browser to open on. It runs scripts and uses the network.

Is the invisible-playwright skill free?

The skill is released under the MIT licence. The source does not mention pricing, so check the project page for any other terms.

Why does the agent use curl instead of the browser sometimes?

The skill says that for a plain download or an API call, exec with curl is simpler. The browser is only used when a task needs a website.

Are my logins saved between uses?

Yes. An identity's profile, cookies and logins stay on disk when it is closed, so they persist between uses. Do not use this skill for sensitive accounts unless you accept that risk.

What should I avoid asking the agent to do with it?

Do not use it to create accounts on sites or to evade their anti-bot rules without permission, since that may breach terms of service and carries legal and ethical risk.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

Use this skill if you are building or running an agent that must work across several website accounts and needs each account kept separate. Pick something else if a file download or API call will do the job, since the skill itself says curl is simpler, or if you need to handle sensitive accounts, because logins persist on disk.

Download the skill