browser-use

Fast, persistent browser automation via `browser-use` CLI (sessions persist across commands). Use for multi-step web workflows (open -> state -> click/input -> verify -> repeat). Supports chromium/headed, real Chrome (logged-in), and remote browser.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

100%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.

An exemplary CLI skill body: concise, fully executable, with a clear sequenced workflow and explicit validation guidance. No bundle files are needed given the compact, well-sectioned content.

Dimension	Reasoning	Score
Conciseness	The body is lean: short bullets and copy-paste command blocks with no padding or explanation of concepts Claude already knows; every token earns its place.	5 / 5
Actionability	Install, Core Loop, Modes, Common Commands, and Sessions are all fully executable, copy-paste-ready commands covering the common cases.	5 / 5
Workflow Clarity	The Core Loop is explicitly sequenced (open -> state -> act -> screenshot -> state verify -> close) with a validation checkpoint, and the Rules section enforces re-running `state` before acting as a feedback loop.	5 / 5
Progressive Disclosure	No bundle files exist and none are needed; content is ~75 lines organized into clearly headed sections (Purpose, When, Install, Core Loop, Modes, Commands, Sessions, Rules) with easy navigation.	5 / 5
	Total	20 / 20 Passed

Description

92%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.

A strong description: third-person, concrete, and explicit about both capabilities and when to use it. Minor trigger-term synonym coverage is the only gap.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete actions ("open -> state -> click/input -> verify -> repeat") and concrete modes (chromium/headed, real Chrome, remote), giving comprehensive coverage of what the skill does.	5 / 5
Completeness	It states a clear "what" ("Fast, persistent browser automation via `browser-use` CLI") and an explicit "Use for multi-step web workflows ..." trigger clause, answering both what and when with concrete triggers.	5 / 5
Trigger Term Quality	Natural terms like "browser automation", "multi-step web workflows", and "logged-in Chrome" are present, but common synonyms a user might say (e.g. scraping, headless browser, automate browser) are missing.	4 / 5
Distinctiveness Conflict Risk	It targets a specific CLI (browser-use) with distinct mode triggers (chromium/headed/real Chrome/remote), occupying a clear niche with minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: marchatton/agent-skills
Path: .agents/skills/00-utilities/browser-use/SKILL.md
Commit: a0eadb2

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.