Skip to content
FunCoding

Search

Search docs, Skills and MCP

invisible-playwright

浏览器自动化32kinvisible_engine_dots/skills/invisible-playwright/SKILL.md

Install

Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.

读取 https://funcoding.ai/skills/feder-cr/invisible_dots/invisible-playwright/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.md

The browser

Your browser is invisible_playwright: a real Firefox that a site sees as a person at a computer. Everything you do in it goes through the real pointer and the real keyboard. Use it when a task needs a website; for a plain download or an API, exec with curl is simpler.

Identities

A browser identity is one person on the web: its own profile, cookies, logins and fingerprint, kept on disk between uses.

  • browser_identity_list shows the identities, which are open, and how many may be open at once.
  • browser_identity_create makes one, closed. Give it a name only: it then leaves through this computer's own network, which is right unless the person asked for this one identity to use a proxy of theirs.
  • browser_identity_launch opens it on your desktop. The first launch of a new identity can take minutes.
  • browser_identity_close closes it; its profile, cookies and logins stay.
  • Reuse the identity that is already logged in to a site instead of making a new one, and keep one identity per person or account you act as: two accounts in one identity are one person to anyone looking.
  • A second identity is for what must not touch the first. The usual case: signing up somewhere and needing a mailbox for the verification. Open a throwaway-mail site in another identity, take the address, type it into the form in the first one, and go back to the other for the link.

Each open identity drives one page. browser_navigate opens a url in it, and every other tool acts on that page. Going somewhere else and coming back is a navigation, not a second window.

Acting on a page: try things in this order

The order matters, because a page can tell the difference.

  1. A named tool with a selector: browser_click, browser_type, browser_select_option, browser_press_key. browser_snapshot gives the selector of each visible element; pass it as it is, it is built to be unambiguous.
  2. Coordinates. browser_snapshot reports at: [x, y] for every element it lists, in viewport pixels, and browser_click_at takes exactly those. This is for what a selector does not describe: a canvas, a slider, a map, a widget made of plain boxes.
  3. Your eyes. browser_screenshot, find the thing in the picture, then browser_click_at where it is. For what the snapshot does not list at all. computer_screenshot shows your whole desktop, the browser window included.

Read with browser_snapshot (title, url and the interactive elements, with checked and value where they have one) and browser_read_text (the text of an element). browser_scroll, browser_back, browser_forward and browser_reload move around as a person would.

Never try to change a page except through the pointer and the keyboard: an event a script makes arrives marked as not coming from a person, which is the clearest sign that a bot is driving.

When it does not work

  • If a tool says the browser is not open or is gone, launch the identity again and carry on.
  • A date field that is a calendar wants its days clicked, not typed.
  • A captcha, a block or a page that keeps refusing you: say so in your answer, with what you saw. A task reported as impossible is worth more than one done in a way that gets the identity blocked.
  • Do not guess a number or a fact you could not read on the page.

Close an identity with browser_identity_close once the task no longer needs it, before you answer: an open browser holds memory on your computer.

Your own skills

When you work out how to do something on a site that you will do again (where its login is, which steps a form needs, what blocks you), write it down as a skill of your own: /home/dot/skills//SKILL.md, the same shape as this file.

Similar Skills

webapp-testing
anthropics/skills180k

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

Browser automation

browser-testing-with-devtools
addyosmani/agent-skills103k

browser-testing-with-devtools

Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.

Browser automation

webapp-testing
ComposioHQ/awesome-claude-skills77k

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

Browser automation

browser
code-yeongyu/oh-my-openagent70k

browser

Drives a real browser through the omowright library from the js eval kernel: sites the user is already signed into, forms and clicks, JS-rendered pages, screenshots, web QA, extension popups, a human handoff for login, CAPTCHA or OTP, and a browser you own for scraping, bot-scored targets, network capture and QA traces. Use for any interactive browser task; not for a plain search or an unblocked static fetch.

Browser automation

agent-browser
shanraisshan/claude-code-best-practice67k

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

Browser automation

cherry-regression-test
CherryHQ/cherry-studio52k

cherry-regression-test

Run Cherry Studio critical-path system regression tasks through the repository-owned Playwright E2E workflow. Use for full regression, release acceptance, development-branch system validation, or a named cherry-regression-test task on GitHub-hosted macOS and Windows runners.

Browser automation