agentleFS
nearthinknearthink/agent-skills/skills/deskclaw-browser/SKILL.md

agent-browser

Skill0 starsChanged 8 months agoMITView on GitHub

Self-contained browser automation. Navigates websites, fills forms, takes screenshots, extracts data. Runtime auto-installs on first use — no npm, Node.js, or Chrome required on the host.

190 other projects use a version of this, 19 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use time-skill, dep-refs and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Recepay6358Skill

    time-skill

    Display the current time in Pakistan Standard Time (PKT, UTC+5). Use when the user asks for the current time, Pakistan time, or PKT.

    Also in 6 projects that use this

  • betacatslingSkill

    dep-refs

    Use when needs to inspect TypeScript export references in the z-code workspace, list exports from a file, verify whether an export is unused before deletion, investigate who imports a symbol during refactors, or combine pnpm knip unused-export results with pnpm dep:refs symbol-level reference tracing.

    Also in 5 projects that use this

  • betacatslingSkill

    feature-boundary-planner

    Map a ZCode behavior change to current UI surfaces, state owners, protocol commands, persistence, and validation. Use for impact analysis, product-boundary planning, or an implementation handoff grounded in the checked-out source.

    Also in 5 projects that use this

  • nicepkgSkill

    community-led-growth

    Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.

    Also in 5 projects that use this

  • nicepkgSkill

    ph-community-outreach

    Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.

    Also in 5 projects that use this

  • Recepay6358Skill

    weather-svg-creator

    Creates an SVG weather card showing the current temperature for Dubai. Writes the SVG to orchestration-workflow/weather.svg and updates orchestration-workflow/output.md.

    Also in 6 projects that use this

  • +3 more from nicepkg

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 173 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before executing ANY agent-browser command, you MUST ensure the runtime is installed:

    line 14
  2. Very specific:

    Check if runtime/version.txt exists in this skill's directory

    line 16
  3. Distinctive:

    If it does NOT exist, run the bootstrap script:

    line 17
  4. Distinctive:

    After bootstrap, ALL commands must go through the wrapper:

    line 21
  5. Very specific:

    NEVER call agent-browser directly without the skill directory prefix.

    line 27

“Common” is measured: kept by at least 6 in 10 of the 173 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Browser Automation with agent-browser

Runtime Setup (MANDATORY — run before any command)

Before executing ANY agent-browser command, you MUST ensure the runtime is installed:

  1. Check if runtime/version.txt exists in this skill's directory
  2. If it does NOT exist, run the bootstrap script:
    • macOS / Linux: bash "<SKILL_DIR>/bootstrap.sh"
    • Windows: powershell -ExecutionPolicy Bypass -File "<SKILL_DIR>/bootstrap.ps1" This downloads ~230MB runtime (one-time). Tell the user: "正在首次准备浏览器环境,请稍候..."
  3. After bootstrap, ALL commands must go through the wrapper:
    • macOS / Linux: "<SKILL_DIR>/agent-browser" <command> [args...]
    • Windows: "<SKILL_DIR>/agent-browser.cmd" <command> [args...]

Replace <SKILL_DIR> with the absolute path to this skill's directory.

NEVER call agent-browser directly without the skill directory prefix. Always use "<SKILL_DIR>/agent-browser" (macOS/Linux) or "<SKILL_DIR>/agent-browser.cmd" (Windows).

Quick start

"<SKILL_DIR>/agent-browser" open <url>        # Navigate to page
"<SKILL_DIR>/agent-browser" snapshot -i       # Get interactive elements with refs
"<SKILL_DIR>/agent-browser" click @e1         # Click element by ref
"<SKILL_DIR>/agent-browser" fill @e2 "text"   # Fill input by ref
"<SKILL_DIR>/agent-browser" close             # Close browser

Core workflow

  1. Navigate: "<SKILL_DIR>/agent-browser" open <url>
  2. Snapshot: "<SKILL_DIR>/agent-browser" snapshot -i (returns elements with refs like @e1, @e2)
  3. Interact using refs from the snapshot
  4. Re-snapshot after navigation or significant DOM changes

Command Reference

Below, AB is shorthand for "<SKILL_DIR>/agent-browser". Replace <SKILL_DIR> with the absolute path to this skill's directory in every invocation.

Navigation

"<SKILL_DIR>/agent-browser" open <url>
"<SKILL_DIR>/agent-browser" back
"<SKILL_DIR>/agent-browser" forward
"<SKILL_DIR>/agent-browser" reload
"<SKILL_DIR>/agent-browser" close
"<SKILL_DIR>/agent-browser" connect 9222    # Connect via CDP port

Snapshot (page analysis)

"<SKILL_DIR>/agent-browser" snapshot            # Full accessibility tree
"<SKILL_DIR>/agent-browser" snapshot -i         # Interactive elements only (recommended)
"<SKILL_DIR>/agent-browser" snapshot -c         # Compact output
"<SKILL_DIR>/agent-browser" snapshot -d 3       # Limit depth to 3
"<SKILL_DIR>/agent-browser" snapshot -s "#main" # Scope to CSS selector

Interactions (use @refs from snapshot)

"<SKILL_DIR>/agent-browser" click @e1
"<SKILL_DIR>/agent-browser" dblclick @e1
"<SKILL_DIR>/agent-browser" fill @e2 "text"     # Clear and type
"<SKILL_DIR>/agent-browser" type @e2 "text"     # Type without clearing
"<SKILL_DIR>/agent-browser" press Enter
"<SKILL_DIR>/agent-browser" hover @e1
"<SKILL_DIR>/agent-browser" check @e1
"<SKILL_DIR>/agent-browser" uncheck @e1
"<SKILL_DIR>/agent-browser" select @e1 "value"
"<SKILL_DIR>/agent-browser" scroll down 500
"<SKILL_DIR>/agent-browser" scrollintoview @e1
"<SKILL_DIR>/agent-browser" drag @e1 @e2
"<SKILL_DIR>/agent-browser" upload @e1 file.pdf

Get information

"<SKILL_DIR>/agent-browser" get text @e1
"<SKILL_DIR>/agent-browser" get html @e1
"<SKILL_DIR>/agent-browser" get value @e1
"<SKILL_DIR>/agent-browser" get attr @e1 href
"<SKILL_DIR>/agent-browser" get title
"<SKILL_DIR>/agent-browser" get url
"<SKILL_DIR>/agent-browser" get count ".item"

Screenshots & PDF

"<SKILL_DIR>/agent-browser" screenshot
"<SKILL_DIR>/agent-browser" screenshot path.png
"<SKILL_DIR>/agent-browser" screenshot --full    # Full page
"<SKILL_DIR>/agent-browser" pdf output.pdf

Wait

"<SKILL_DIR>/agent-browser" wait @e1
"<SKILL_DIR>/agent-browser" wait 2000
"<SKILL_DIR>/agent-browser" wait --text "Success"
"<SKILL_DIR>/agent-browser" wait --url "**/dashboard"
"<SKILL_DIR>/agent-browser" wait --load networkidle

Semantic locators

"<SKILL_DIR>/agent-browser" find role button click --name "Submit"
"<SKILL_DIR>/agent-browser" find text "Sign In" click
"<SKILL_DIR>/agent-browser" find label "Email" fill "user@test.com"

Cookies & Storage

"<SKILL_DIR>/agent-browser" cookies
"<SKILL_DIR>/agent-browser" cookies set name value
"<SKILL_DIR>/agent-browser" cookies clear
"<SKILL_DIR>/agent-browser" storage local

Tabs

"<SKILL_DIR>/agent-browser" tab
"<SKILL_DIR>/agent-browser" tab new [url]
"<SKILL_DIR>/agent-browser" tab 2
"<SKILL_DIR>/agent-browser" tab close

Dialogs

"<SKILL_DIR>/agent-browser" dialog accept [text]
"<SKILL_DIR>/agent-browser" dialog dismiss

JavaScript

"<SKILL_DIR>/agent-browser" eval "document.title"

Global options

"<SKILL_DIR>/agent-browser" --session <name> ...    # Isolated browser session
"<SKILL_DIR>/agent-browser" --json ...              # JSON output for parsing
"<SKILL_DIR>/agent-browser" --headed ...            # Show browser window
"<SKILL_DIR>/agent-browser" --proxy <url> ...       # Use proxy server

Example: Form submission

"<SKILL_DIR>/agent-browser" open https://example.com/form
"<SKILL_DIR>/agent-browser" snapshot -i
"<SKILL_DIR>/agent-browser" fill @e1 "user@example.com"
"<SKILL_DIR>/agent-browser" fill @e2 "password123"
"<SKILL_DIR>/agent-browser" click @e3
"<SKILL_DIR>/agent-browser" wait --load networkidle
"<SKILL_DIR>/agent-browser" snapshot -i

Example: Authentication with saved state

"<SKILL_DIR>/agent-browser" open https://app.example.com/login
"<SKILL_DIR>/agent-browser" snapshot -i
"<SKILL_DIR>/agent-browser" fill @e1 "username"
"<SKILL_DIR>/agent-browser" fill @e2 "password"
"<SKILL_DIR>/agent-browser" click @e3
"<SKILL_DIR>/agent-browser" wait --url "**/dashboard"
"<SKILL_DIR>/agent-browser" state save auth.json

# Later: load saved state
"<SKILL_DIR>/agent-browser" state load auth.json
"<SKILL_DIR>/agent-browser" open https://app.example.com/dashboard

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.