pi-browser-use

What pi-browser-use does, in the publisher's words

From the project README, punctuation lightly normalized · Open the README on GitHub →

Links

• github.com/0xPlayerOne/pi-browser-use
• plugin.json (manifest)

Skills · 8

auth-bootstrap

Initialize or reauthenticate the managed persistent browser profile. Use on a new machine or plugin instance, at a login wall, or when SSO, 2FA, passkeys or provider verification require a human. Works with native Pi and portable MCP hosts.

browser-policy

Browser-use policy for agents. Use before any browser_* tool call. Prefer CLIs and APIs over browser automation, default to a dedicated persistent headless profile, use fresh mode for anonymous checks, and never steal user focus.

derive-client

Turn observed browser traffic into a standalone API client. Use when a task repeats the same site interactions and should stop driving the browser, record the network calls, then replace clicks with fetch.

dogfood

Exploratory testing playbook for bug hunts and quality passes. Use when asked to dogfood, poke at, or break a site, tour it with intent instead of clicking around.

gmail-auth

Verify Gmail authentication in the persistent managed browser profile. Use when a task needs the Gmail inbox, after browser_setup, or when Google shows a login or verification challenge.

playwright-handoff

Decide when browser automation has hit its limits and hand off to a repo Playwright run instead. Use when a task needs request mocking, assertions, traces, repeatability, or CI parity that browser_* tools cannot provide.

triage-console

Standard flow for diagnosing a broken page. Use when a site misbehaves, renders wrong, or throws, snapshot, console errors, failed network requests, then screenshot.

visual-qa

Screenshot discipline for visual checks of WebGL/canvas scenes and layouts. Use when asked whether something \"looks right\", for before/after comparisons, or for viewport coverage.

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.

MCP servers · 1

browserstdio

node ${PLUGIN_ROOT}/dist/mcp-server.js

env vars: PI_BROWSER_USE_DATA_DIR

Read from the plugin's own mcp.json. We list environment variable names, never values.

Category

Other. Assigned by this directory. Agent Plugins 1.0.0 has no category field, so no manifest declares one.

Keywords

browser · chrome · mcp · agent-skills · pi

Related by publisher and keywords

• pi-cloudflare0xPlayerOne

  Cloudflare skills: the official Cloudflare skills library plus cf-first hardening and cf CLI skills. Tools live in the cf CLI, not in this plugin.

• chrome-devtoolsChromeDevTools

  Reliable Chrome automation, debugging, and performance analysis for AI agents.

• tidesurfTideSurf

  TideSurf launches or attaches to Chromium over CDP and compresses the live DOM into token-efficient text for browser agents, exposed via CLI and MCP.

• chrome-devtools777genius

  Community package for Chrome DevTools MCP. Inspect pages, automate flows, analyze performance, and debug browser state.

• centricmem-skillzeyu-j

  Hosted CentricMem librarian: organise and retrieve Markdown memory via host MCP.

• automate-browserfarazpawle

  Let your agent use your real, logged-in browser in its own background tab, 46 tools plus the automate-browser skill covering tab ownership, page interaction, extraction, sessions, capture and troubleshooting.