Browser
- 582 installs
- 67k repo stars
- Updated August 4, 2026
- ruvnet/ruflo
browser is a Claude Code skill (version 1.0.0) that automates web browsers for claude-flow agents using agent-browser CLI with AI-optimized snapshots that reduce context by 93% via element refs like @e1 and @e2.
About
browser is a Claude Code skill from ruvnet/ruflo (version 1.0.0) for web browser automation using agent-browser with AI-optimized accessibility snapshots. Instead of dumping full DOM trees, the skill returns element refs (@e1, @e2) that reduce agent context by 93%. The workflow runs agent-browser open, snapshot -i for interactive elements, then click, fill, and screenshot commands before close. Developers and claude-flow agents invoke browser for scraping, navigation, form interaction, and visual verification. Triggers include /browser, browse, web automation, scrape, navigate, and screenshot.
- browser
Browser by the numbers
- 582 all-time installs (skills.sh)
- +6 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #702 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ruvnet/ruflo --skill browserAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 582 |
|---|---|
| repo stars | ★ 67k |
| Last updated | August 4, 2026 |
| Repository | ruvnet/ruflo ↗ |
How do agents automate browsers with minimal context?
Use browser for development tasks
Who is it for?
Developers running claude-flow or agent-browser workflows who need compact web automation snapshots instead of full DOM context.
Skip if: Developers who need production Playwright or Cypress test suites with assertions, fixtures, and CI integration.
When should I use this skill?
An agent needs to open a URL, snapshot interactive elements, click, fill forms, or capture screenshots via /browser triggers.
What you get
Accessibility snapshots with element refs, interaction logs, screenshots, and closed browser sessions
- Accessibility snapshots
- Screenshots
- Browser interaction traces
By the numbers
- Skill version 1.0.0
- Reduces browser context by 93% using element refs
- Exposes 6 browser automation tools: open, snapshot, click, fill, screenshot, close
Files
Browser Automation Skill
Web browser automation using agent-browser with AI-optimized snapshots. Reduces context by 93% using element refs (@e1, @e2) instead of full DOM.
Core Workflow
# 1. Navigate to page
agent-browser open <url>
# 2. Get accessibility tree with element refs
agent-browser snapshot -i # -i = interactive elements only
# 3. Interact using refs from snapshot
agent-browser click @e2
agent-browser fill @e3 "text"
# 4. Re-snapshot after page changes
agent-browser snapshot -iQuick Reference
Navigation
| Command | Description |
|---|---|
open <url> | Navigate to URL |
back | Go back |
forward | Go forward |
reload | Reload page |
close | Close browser |
Snapshots (AI-Optimized)
| Command | Description |
|---|---|
snapshot | Full accessibility tree |
snapshot -i | Interactive elements only (buttons, links, inputs) |
snapshot -c | Compact (remove empty elements) |
snapshot -d 3 | Limit depth to 3 levels |
screenshot [path] | Capture screenshot (base64 if no path) |
Interaction
| Command | Description |
|---|---|
click <sel> | Click element |
fill <sel> <text> | Clear and fill input |
type <sel> <text> | Type with key events |
press <key> | Press key (Enter, Tab, etc.) |
hover <sel> | Hover element |
select <sel> <val> | Select dropdown option |
check/uncheck <sel> | Toggle checkbox |
scroll <dir> [px] | Scroll page |
Get Info
| Command | Description |
|---|---|
get text <sel> | Get text content |
get html <sel> | Get innerHTML |
get value <sel> | Get input value |
get attr <sel> <attr> | Get attribute |
get title | Get page title |
get url | Get current URL |
Wait
| Command | Description |
|---|---|
wait <selector> | Wait for element |
wait <ms> | Wait milliseconds |
wait --text "text" | Wait for text |
wait --url "pattern" | Wait for URL |
wait --load networkidle | Wait for load state |
Sessions
| Command | Description |
|---|---|
--session <name> | Use isolated session |
session list | List active sessions |
Selectors
Element Refs (Recommended)
# Get refs from snapshot
agent-browser snapshot -i
# Output: button "Submit" [ref=e2]
# Use ref to interact
agent-browser click @e2CSS Selectors
agent-browser click "#submit"
agent-browser fill ".email-input" "test@test.com"Semantic Locators
agent-browser find role button click --name "Submit"
agent-browser find label "Email" fill "test@test.com"
agent-browser find testid "login-btn" clickExamples
Login Flow
agent-browser open https://example.com/login
agent-browser snapshot -i
agent-browser fill @e2 "user@example.com"
agent-browser fill @e3 "password123"
agent-browser click @e4
agent-browser wait --url "**/dashboard"Form Submission
agent-browser open https://example.com/contact
agent-browser snapshot -i
agent-browser fill @e1 "John Doe"
agent-browser fill @e2 "john@example.com"
agent-browser fill @e3 "Hello, this is my message"
agent-browser click @e4
agent-browser wait --text "Thank you"Data Extraction
agent-browser open https://example.com/products
agent-browser snapshot -i
# Iterate through product refs
agent-browser get text @e1 # Product name
agent-browser get text @e2 # Price
agent-browser get attr @e3 href # LinkMulti-Session (Swarm)
# Session 1: Navigator
agent-browser --session nav open https://example.com
agent-browser --session nav state save auth.json
# Session 2: Scraper (uses same auth)
agent-browser --session scrape state load auth.json
agent-browser --session scrape open https://example.com/data
agent-browser --session scrape snapshot -iIntegration with Claude Flow
MCP Tools
All browser operations are available as MCP tools with browser/ prefix:
browser/openbrowser/snapshotbrowser/clickbrowser/fillbrowser/screenshot- etc.
Memory Integration
# Store successful patterns
npx @claude-flow/cli memory store --namespace browser-patterns --key "login-flow" --value "snapshot->fill->click->wait"
# Retrieve before similar task
npx @claude-flow/cli memory search --query "login automation"Hooks
# Pre-browse hook (get context)
npx @claude-flow/cli hooks pre-edit --file "browser-task.ts"
# Post-browse hook (record success)
npx @claude-flow/cli hooks post-task --task-id "browse-1" --success trueTips
1. Always use snapshots - They're optimized for AI with refs 2. Prefer `-i` flag - Gets only interactive elements, smaller output 3. Use refs, not selectors - More reliable, deterministic 4. Re-snapshot after navigation - Page state changes 5. Use sessions for parallel work - Each session is isolated
Related skills
Lark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.493k
Lark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.387k16kLark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.386k16k
Just ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k41Lark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.235k16k
Design An InterfaceGenerate multiple radically different interface or API designs in parallel before committing to one.188k198kForks & variants (1)
Browser has 1 known copy in the catalog totaling 55 installs. They canonicalize to this original listing.
- proffesor-for-testing - 55 installs
How it compares
Pick browser over full DOM scraping skills when claude-flow agents need compact accessibility snapshots and element-ref interactions.
FAQ
How does browser reduce agent context usage?
The browser skill uses agent-browser accessibility snapshots with compact element refs like @e1 and @e2 instead of full DOM dumps. The README states this reduces context by 93%, letting claude-flow agents interact via click and fill on referenced elements.
What commands does the browser skill expose?
The browser skill wraps six agent-browser tools: browser/open, browser/snapshot, browser/click, browser/fill, browser/screenshot, and browser/close. The typical workflow opens a URL, snapshots interactive elements with -i, interacts, then closes.
When should developers invoke browser?
Developers invoke browser when claude-flow agents need web automation for navigation, scraping, form fills, or screenshots. Triggers include /browser, browse, web automation, scrape, navigate, and screenshot keywords in agent sessions.