agentleFS
Sign inStart free
SentryKnown publishergetsentry/junior/packages/junior-agent-browser/skills/agent-browser/SKILL.md

agent-browser

Skill394 starsChanged 7 months agoApache-2.0View on GitHub

Automate websites with the agent-browser CLI for navigation, form flows, screenshots, extraction, and repeatable browser tasks. Use when users ask to interact with web apps, gather evidence from pages, or run browser-based QA steps.

We split this skill into the rules it gives an agent

9 rules. 0 are common, 4 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 171 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when work requires real browser interaction instead of API-only lookups.

    line 8
  2. Very specific:

    Use agent-browser directly.

    line 35
  3. Distinctive:

    Prefer one named session for multi-step flows:

    line 36
  4. Very specific:

    Use chained commands with && only when no intermediate output is needed.

    line 38
  5. Distinctive:

    If page load is async-heavy, wait explicitly:

    line 40
  6. Very specific:

    When a user asks to see/share a screenshot in Slack, use sendFiles with the screenshot path in files so the image is included in the active …

    line 43
  7. Very specific:

    Never claim a screenshot was shared unless sendFiles returned success in this turn.

    line 44
  8. Very specific:

    If sendFiles is unavailable or file attachment fails, state the failure clearly and include the saved screenshot path or error instead of …

    line 45
  9. Distinctive:

    Read only what is needed:

    line 71

“Common” is measured: kept by at least 6 in 10 of the 171 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

Use this skill when work requires real browser interaction instead of API-only lookups.

Core Workflow

  1. Open target page:
  • agent-browser open <url>
  1. Capture interactive refs:
  • agent-browser snapshot -i
  1. Interact by ref:
  • agent-browser click @e1
  • agent-browser fill @e2 "value"
  1. Re-snapshot after every navigation or significant DOM change:
  • agent-browser snapshot -i
  1. Capture result evidence:
  • agent-browser screenshot --annotate <file.png>

Operational Rules

  • Use agent-browser directly; do not use npx agent-browser.
  • Prefer one named session for multi-step flows:
    • agent-browser --session <name> ...
  • Use chained commands with && only when no intermediate output is needed.
  • For commands that need refs (@e*), run snapshot -i first and use fresh refs.
  • If page load is async-heavy, wait explicitly:
    • agent-browser wait --load networkidle
  • For user-facing findings, include screenshots and the exact page URL.
  • When a user asks to see/share a screenshot in Slack, use sendFiles with the screenshot path in files so the image is included in the active conversation.
  • Never claim a screenshot was shared unless sendFiles returned success in this turn.
  • If sendFiles is unavailable or file attachment fails, state the failure clearly and include the saved screenshot path or error instead of claiming success.

Common Patterns

Form flow

agent-browser --session demo open https://example.com/signup
agent-browser --session demo wait --load networkidle
agent-browser --session demo snapshot -i
agent-browser --session demo fill @e1 "user@example.com"
agent-browser --session demo click @e2
agent-browser --session demo wait --load networkidle
agent-browser --session demo screenshot --annotate /tmp/signup-result.png

Structured extraction

agent-browser open https://example.com
agent-browser snapshot --json > /tmp/page.json
agent-browser get text body > /tmp/page.txt

Reference Files

Read only what is needed:

  • Command surface: references/commands.md
  • Auth vault + login flows: references/authentication.md
  • Session/state persistence: references/session-management.md
  • Snapshot refs and stale-ref handling: references/snapshot-refs.md
  • Proxy/network setup: references/proxy-support.md
  • Recording and video capture: references/video-recording.md
  • Performance profiling: references/profiling.md

Templates

  • Authenticated flow bootstrap: templates/authenticated-session.sh
  • Capture workflow skeleton: templates/capture-workflow.sh
  • Form automation skeleton: templates/form-automation.sh

Download now (ZIP)

  • Other versions188 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 188

    1. shanraisshan/claude-code-best-practice★ 68ksame name
    2. moeru-ai/airi★ 51ksame name
    3. vercel-labs/agent-browser★ 45ksame name
    4. activepieces/activepieces★ 25ksame name
    5. slopus/happy★ 24ksame name
    6. kortix-ai/suna★ 20ksame name
    7. eosphoros-ai/DB-GPT★ 20ksame name
    8. documenso/documenso★ 16ksame name
    9. emdash-cms/emdash★ 14ksame name
    10. elie222/inbox-zero★ 13ksame name

    178 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use dep-refs, feature-boundary-planner 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.
    • 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

    • 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 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

    • ncklrsSkill

      seo-content-strategist

      Expert SEO content strategy for SaaS and B2B sites. Use when doing keyword research, planning content clusters, creating pillar pages, optimizing on-page SEO, fixing technical SEO issues, building links, refreshing content, implementing programmatic SEO, mapping search intent, optimizing for SERP features, or measuring content performance. Use for SEO audits, content gap analysis, and organic growth strategy.

      Also in 5 projects that use this

    • +3 more from nicepkg
  • In this repository42 other files it gives its agents.

Does it work?

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

Reviews can't be read right now.

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.

Check your setup, free