browser-automation
AI browser automation - navigate, interact, extract, verify via browser-use MCP
Best use case
browser-automation is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
AI browser automation - navigate, interact, extract, verify via browser-use MCP
Teams using browser-automation should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/browser-automation/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How browser-automation Compares
| Feature / Agent | browser-automation | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
AI browser automation - navigate, interact, extract, verify via browser-use MCP
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Browser 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`:
```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: test@example.com
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 screenshotsRelated Skills
workflow-router
Goal-based workflow orchestration - routes tasks to specialist agents based on user goals
wiring
Wiring Verification
websocket-patterns
Connection management, room patterns, reconnection strategies, message buffering, and binary protocol design.
visual-verdict
Screenshot comparison QA for frontend development. Takes a screenshot of the current implementation, scores it across multiple visual dimensions, and returns a structured PASS/REVISE/FAIL verdict with concrete fixes. Use when implementing UI from a design reference or verifying visual correctness.
verification-loop
Comprehensive verification system covering build, types, lint, tests, security, and diff review before a PR.
vector-db-patterns
Embedding strategies, ANN algorithms, hybrid search, RAG chunking strategies, and reranking for semantic search and retrieval.
variant-analysis
Find similar vulnerabilities across a codebase after discovering one instance. Uses pattern matching, AST search, Semgrep/CodeQL queries, and manual tracing to propagate findings. Adapted from Trail of Bits. Use after finding a bug to check if the same pattern exists elsewhere.
validate-agent
Validation agent that validates plan tech choices against current best practices
tracing-patterns
OpenTelemetry setup, span context propagation, sampling strategies, Jaeger queries
tour
Friendly onboarding tour of Claude Code capabilities for users asking what it can do.
tldr-stats
Show full session token usage, costs, TLDR savings, and hook activity
tldr-router
Map code questions to the optimal tldr command by detecting intent and routing to the right analysis layer.