CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

90

2.62x
Quality

89%

Does it follow best practices?

Impact

92%

2.62x

Average score across 6 eval scenarios

SecuritybySnyk

Critical

Do not install without reviewing

The canonical home for this skill is agent-browser in vercel-labs/agent-browser

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced skill body with executable examples and strong workflow/validation guidance. The main defect is progressive disclosure: dead reference and template links, plus a large inline command reference that should be split out, undercut an otherwise clean one-level-deep structure.

Suggestions

Create references/commands.md and references/profiling.md (or remove those rows from the Deep-Dive Documentation table) so every linked file resolves.

Ship the templates/ directory referenced in 'Ready-to-Use Templates' or delete that section — three dead links currently point at nonexistent files.

Move the bulk 'Essential Commands' block into references/commands.md, keeping only the handful of commands needed for the Core Workflow inline in SKILL.md.

DimensionReasoningScore

Conciseness

The body is dense and command-focused with almost no explanation of concepts Claude already knows, e.g. the Essential Commands section is pure executable reference. Not 5 because the ~55-line inline Essential Commands block duplicates material that belongs in the (linked) full command reference, and the "Why this matters" paragraph under eval re-explains shell quoting behavior at length.

4 / 5

Actionability

Nearly every section is copy-paste-ready with real flags and worked end-to-end examples — e.g. "agent-browser open https://example.com && agent-browser wait --load networkidle && agent-browser snapshot -i", the eval "--stdin <<'EVALEOF'" heredoc pattern, and concrete guidance on when to chain vs. run separately. Common cases are covered with specific commands and expected output.

5 / 5

Workflow Clarity

The Core Workflow (Navigate → Snapshot → Interact → Re-snapshot) is stated up front and reinforced by a dedicated "Ref Lifecycle (Important)" section, the diff workflow ("snapshot -> action -> diff") provides an explicit verification loop, and timeout/slow-page plus session-cleanup guidance closes the sequence. Re-snapshotting after DOM changes is the explicit validation checkpoint for this skill's fragile operation (stale refs).

5 / 5

Progressive Disclosure

Structure and signaling are good — a Deep-Dive Documentation table with when-to-use guidance, and five real reference files — but two of the seven linked references (references/commands.md, references/profiling.md) do not exist, and all three templates/*.sh links point to a nonexistent templates/ directory. Additionally, the bulk Essential Commands reference is inlined in SKILL.md instead of living in the separate commands file it links to. This matches the anchor of structure present but content that should be separate is inline, compounded by dead links.

3 / 5

Total

17

/

20

Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: concrete capabilities, explicit use-when guidance, and abundant natural trigger phrases in third person. The only weakness is the slightly over-broad trailing catch-all clauses that marginally raise conflict risk with adjacent web-interaction skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps" — giving comprehensive, specific coverage of a browser automation CLI rather than vague capability language. Not 4 because coverage spans the full action space of the tool with essentially no gaps.

5 / 5

Completeness

Both halves are explicit: the what is "Browser automation CLI for AI agents" with the concrete action list, and the when is "Use when the user needs to interact with websites... Triggers include requests to..." with concrete trigger phrases. This mirrors the 5 anchor exactly.

5 / 5

Trigger Term Quality

Quotes eight natural phrases a user would actually say: "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions". This includes synonyms for the same capability (screenshot/capture, scrape/extract), matching the comprehensive-synonyms anchor.

5 / 5

Distinctiveness Conflict Risk

The browser-automation niche is clear and most triggers ("open a website", "take a screenshot") are distinct, but the trailing catch-alls "automating any browser task" and "any task requiring programmatic web interaction" invite overlap with scraping, API-testing, and general web-fetch skills. Not 3 because the core triggers are unmistakably browser-specific; not 5 because the over-broad tail clauses dilute the niche.

4 / 5

Total

19

/

20

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (540 lines); consider splitting into references/ and linking

Warning

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

relative_links

Relative link issues: 5 missing

Warning

referenced_paths_exist

Referenced path issues: 4 missing

Warning

Total

12

/

16

Passed

Repository

rivet-dev/sandbox-agent

Path

sandbox-agent/.agents/skills/agent-browser/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.