SkillAgentSearch skills...

browser-automation

Use when controlling web pages with the OpenClaw browser tool, especially multi-step flows, login checks, tab management, or recovery from stale refs/timeouts.

Install / Use

npx skills add krsnaceng07/jarvis --skill browser-automation

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

74/100

Category

Automation

Supported Platforms

Universal

Our assessment of browser-automation

browser-automation scores 74/100 on our quality scale, 2544th of 2,771 Automation skills we index.

Its SKILL.md is 5.3 KB long, split into 6 sections with 4 code examples: a solid amount of guidance for an agent.

It has no GitHub stars yet, so there is no community track record; judge it on its content.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
0/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 3 days ago, so browser-automation is actively maintained.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 80/100, with 2 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

browser-automation compared with similar skills

All 4 of these similar skills score higher than browser-automation; compare them before choosing.

SkillScoreStarsUpdatedFormat
browser-automation (this skill)by krsnaceng077403d agoSKILL.md
Agent-Reachby Panniantong100113.3k12d agoCLAUDE.md
rufloby ruvnet10082.1ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10040.2k10d agoCLAUDE.md
Scraplingby D4Vinci100104.4k2d agoMCP Server

Frequently asked questions

How do I install browser-automation?
Run npx skills add krsnaceng07/jarvis --skill browser-automation. The install tabs above show the steps for each supported agent.
Which AI agents does browser-automation work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is browser-automation safe to use?
It declares no license and scores 80/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is browser-automation still maintained?
The repository was last updated 3 days ago, so browser-automation is actively maintained.

name: browser-automation description: Use when controlling web pages with the OpenClaw browser tool, especially multi-step flows, login checks, tab management, or recovery from stale refs/timeouts. user-invocable: false

Browser Automation

Use this skill when you need the browser tool for anything beyond a single page check.

Operating Loop

  1. Check browser state before acting:
    • openclaw browser doctor or action="status" when the browser/plugin setup itself may be broken.
    • action="status" for availability.
    • action="profiles" if login state or profile choice matters.
    • action="tabs" before opening a new tab if retries/timeouts may have left windows behind.
  2. Prefer stable tab handles:
    • Open important tabs with label, for example label="meet".
    • After action="tabs" or action="open", store suggestedTargetId and pass it as targetId in later calls.
    • suggestedTargetId is the label when one exists, otherwise the stable tabId handle like t1.
    • Avoid relying on raw DevTools targetId except for immediate diagnostics; it can change under Chromium target replacement.
  3. Read before you click:
    • Use action="snapshot" on the intended targetId.
    • Use the same targetId for follow-up actions so refs stay on the same tab.
    • For durable Playwright refs, request refs="aria" when supported. If you receive axN refs from snapshotFormat="aria", use them only after that same snapshot call; stale or unbound axN refs fail fast and need a fresh snapshot.
    • Use urls=true when link text is ambiguous or a direct navigation target would avoid brittle clicks.
    • Use labels=true on snapshot or screenshot when visual position matters. On Playwright-backed profiles, the response includes an annotations array ({ref, number, role, name?, box}) with each ref's bounding box in the captured image's coordinate space, so you can reason about position without re-snapshotting; screenshot labels can also combine with fullPage=true (CLI: --full-page) to label the whole document, or ref / element to clip to one element. profile="user" and other existing-session (chrome-mcp) profiles render an overlay into page screenshots but do not attach annotations or use the Playwright full-page/ref/element projection helper, so read positions from the labeled image itself on those profiles. The raw-CDP fallback (no Playwright) does not support labeled screenshots at all and returns a 501, so only request labels when Playwright is available.
  4. Act narrowly:
    • Prefer action="act" with a ref from the latest snapshot.
    • After navigation, modal changes, or form submission, snapshot again before the next action.
    • Avoid blind waits. Wait for visible UI state when possible.
  5. Report real blockers:
    • If the page needs login, permission, captcha, 2FA, camera/microphone approval, or another manual step, stop and tell the user exactly what is needed.
    • Do not claim the browser is not logged in just because the current page shows a permission or onboarding dialog. Inspect the visible UI first.

Tab Hygiene

Before creating a tab for a named task, list tabs and reuse an existing matching label or URL when it is still usable.

Example:

{ "action": "tabs" }

If no suitable tab exists:

{ "action": "open", "url": "https://example.com", "label": "task" }

Then target it by label:

{ "action": "snapshot", "targetId": "task", "refs": "aria" }

If a retry creates duplicates, close the extras by tabId:

{ "action": "close", "targetId": "t3" }

Do not pass bare numbers like "2" as targetId. Numeric tab positions are only for the CLI openclaw browser tab select 2 helper; browser tool calls need a suggestedTargetId, label, tabId, or raw target id.

Stale Ref Recovery

If an action fails with a missing or stale ref:

  1. Snapshot the same targetId again.
  2. Find the current visible control.
  3. Retry once with the new ref.
  4. If the UI moved to a blocker state, report the blocker instead of looping.

Existing User Browser

Use profile="user" only when existing cookies/login matter. This attaches to the user's running Chromium-based browser.

On macOS, action="importprofile" is the alternative when the agent should use an isolated managed browser with cookies copied from a real Chrome-family profile. First use action="profiles" and inspect systemProfiles, then import into a fresh managed profile name. Import asks for one Keychain/Touch ID consent prompt. It copies cookies, not local storage or IndexedDB; device-bound session credentials (DBSC) mean some Google sessions may still require re-authentication.

For profile="user" and other existing-session profiles, omit timeoutMs on act:type, hover, scrollIntoView, drag, select, and fill; that driver rejects per-call timeout overrides for those actions. act:evaluate accepts timeoutMs.

Google Meet Notes

When creating or joining a Meet:

  • Treat camera/microphone permission screens as progress, not login failure.
  • If asked whether people can hear you, click the microphone option when voice is required.
  • If Google asks for sign-in, 2FA, account chooser confirmation, or permission that needs user approval, report the exact manual action.
  • Use one labeled tab per meeting flow, for example label="meet", and reuse it during retries.

Related Skills

View on GitHub
GitHub Stars0
CategoryAutomation
Updated3d ago
Forks0

Trust signals

80/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium1 low