browser-use

Use PilotDeck's browser-use plugin for browser automation, screenshots, form filling, and web UI checks.

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/browser-use/SKILL.md

Quality

Content

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

The body is highly actionable, with executable install/config commands and a clear check-before-install workflow supported by validation checkpoints. Its main weakness is conciseness — several prose paragraphs restate the adjacent code and explain rationale that could be trimmed.

Suggestions

Trim prose that restates the adjacent bash blocks (e.g. the sentence after the cache-check block) and keep only the non-obvious rationale to lift conciseness.

Replace the '/path/to/PilotDeck' placeholder with the concrete discovery step ('pilotdeck status' then 'cd ~/.pilotdeck/app') already documented below, so the primary install path is fully copy-pasteable.

Add an explicit recovery loop for a failed launch (detect missing executable → run install:browser → re-launch) to turn the implicit checkpoints into a visible feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and the PilotDeck-specific env vars and install commands earn their place, but prose passages restate what the bash blocks already show and add rationale padding, fitting the 'mostly efficient but could be tightened' anchor.	3 / 5
Actionability	It provides concrete, copy-paste-ready bash (cache check, pnpm install, install.sh opt-in) and named env vars with defaults, with only minor gaps like the '/path/to/PilotDeck' placeholder, matching 'mostly executable guidance' rather than fully covering every case at 5.	4 / 5
Workflow Clarity	The Availability section lays out a clear check-first-then-install sequence with an explicit 'Only install when all of the following are true' checklist and a cache-validation checkpoint, fitting 'clear sequence with most checkpoints present' despite a couple of implicit recovery steps.	4 / 5
Progressive Disclosure	Content is a single well-sectioned file (Availability, Runtime Configuration, Usage Notes, Common Checks) with no bundle files and no need for external references, giving good structure with only minor organization gaps rather than the idealized 5-overview-with-references anchor.	4 / 5
	Total	15 / 20 Passed

Description

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

The description is specific and reasonably distinct, naming four concrete browser-use actions tied to a named plugin. Its main weakness is the absence of any explicit 'Use when...' trigger guidance, which caps completeness at 3.

Suggestions

Add an explicit trigger clause, e.g. 'Use when a task needs an interactive browser via PilotDeck — local Web UI smoke tests, screenshots, form filling, or DOM inspection — rather than HTTP/curl for static pages.'

Include a couple of natural synonyms or file/URL cues users might say (e.g. 'Web UI checks', 'localhost smoke test') to broaden trigger-term coverage toward 5.

Sharpen distinctiveness by contrasting with ordinary HTTP/file tools in the description itself, so it is less likely to fire for plain scraping tasks.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several concrete actions — 'browser automation, screenshots, form filling, and web UI checks' — with only minor coverage gaps, fitting the 'lists several specific actions' anchor rather than the comprehensive 5.	4 / 5
Completeness	It states a clear 'what' but provides no 'Use when...' clause or equivalent trigger guidance, so per the rubric completeness is capped at 3 even though the capability list is clear.	3 / 5
Trigger Term Quality	'browser automation', 'screenshots', 'form filling', and 'web UI checks' are natural phrases users would say, giving good keyword coverage, though common synonyms/variations are missing so it stops short of 5.	4 / 5
Distinctiveness Conflict Risk	Tying the skill to 'PilotDeck's browser-use plugin' and 'browser automation' gives it a mostly distinct niche with only minor overlap risk against generic web/scraping skills, landing between the 3 and 5 anchors.	4 / 5
	Total	15 / 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: OpenBMB/PilotDeck
Path: skills/browser-use/SKILL.md
Commit: 9a33f4d

Reviewed: 2 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.