Browser Automation Skill for Claude
AI browser automation - navigate, interact, extract, verify via browser-use MCP
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/vibeeval/vibecosystem --skill browser-automationWhat it tells the agent to use
found in the instruction textThe instruction itself
10 sections, as written by the authorBrowser Automation
AI-powered browser automation via browser-use MCP server. Navigate web pages, fill forms, extract content, take screenshots, and verify deployments.
Setup
Add to ~/.mcp.json:
{
"mcpServers": {
"browser-use": {
"command": "uvx",
"args": ["browser-use", "--mcp"]
}
}
}
Restart Claude Code after adding.
Usage
Navigate & Extract
/browser-automation navigate https://docs.example.com
/browser-automation extract https://docs.example.com --format markdown
Form Interaction
/browser-automation fill https://app.example.com/login
email: [email protected]
password: [from env TEST_PASSWORD]
submit: button[type=submit]
Deploy Verification
/browser-automation verify https://myapp.com
- Check: homepage loads (< 3s)
- Check: /api/health returns 200
- Check: login page renders
- Screenshot: homepage, login, dashboard
Screenshot
/browser-automation screenshot https://myapp.com --full-page
/browser-automation screenshot https://myapp.com --element "#hero-section"
Integration Points
| Trigger | How It Helps |
|---------|-------------|
| shipper deploys | Auto-verify live URL, take screenshots |
| e2e-runner needs browser | Natural language browser tests |
| oracle needs deep docs | Navigate multi-page documentation |
| designer needs references | Capture UI patterns from live sites |
| qa-engineer tests forms | Fill and submit forms, verify results |
| growth analyzes competitors | Extract features, pricing, UX patterns |
MCP Tools Available
| Tool | Description |
|------|-------------|
| browser_navigate | Go to a URL |
| browser_click | Click element by selector or text |
| browser_type | Type into input field |
| browser_screenshot | Capture page/element screenshot |
| browser_extract | Extract page content as text/markdown |
| browser_wait | Wait for element or condition |
| browser_evaluate | Execute JavaScript in page context |
| browser_scroll | Scroll page or element |
Rules
- Max 1 request/second to same domain
- Respect robots.txt
- Never store credentials in output
- Timeout: 30 seconds per page
- Retry once on failure, then report error
- Blur sensitive data in screenshots
Other skills for the same job
different authors, same section of the catalogue
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.
Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.
Use when the user explicitly asks for a desktop or system screenshot (full screen, specific app or window, or a pixel region), or when tool-specific capture capabilities are unavailable and an OS-level capture is needed.
A fast Rust-based headless browser automation CLI with Node.js fallback that enables AI agents to navigate, click, type, and snapshot pages via structured commands.
| 所有联网操作必须通过此 skill 处理，包括：搜索、网页抓取、登录后操作、动态页面交互等。 触发场景：用户要求搜索信息、查看网页内容、访问需要登录的网站、操作网页界面、抓取社交媒体内容（小红书、微博、推特等）、读取动态渲染页面、以及任何需要真实浏览器环境的网络任务。
How to use it
Take vibeeval/browser-automation from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.