CtrlK
BlogDocsLog inGet started
Tessl Logo

browser-use

Control the user's Chrome through the existing persistent Node REPL and the Qwen Browser SDK.

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./packages/core/src/skills/bundled/browser-use/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 content is highly actionable with executable code, clear sequencing, and strong validation/feedback loops throughout. Its main limitation is that a sizable chunk of setup and error-handling prose lives inline rather than in a one-level-deep reference file.

DimensionReasoningScore

Conciseness

The body is information-dense and assumes Claude's competence (no explanations of Chrome/Playwright basics), though the Setup prose on Native Messaging host reuse and downgrade handling could be trimmed slightly.

4 / 5

Actionability

Copy-paste-ready JS snippets and shell commands cover setup, tab creation, locators, screenshots, and finalize, with explicit instructions to substitute the absolute skill-base path.

5 / 5

Workflow Clarity

A clear Setup → Interaction → Finish sequence is paired with explicit validation (confirm runtime files exist, SDK checks connection, version-pin checks) and feedback loops (retry connection, re-register MCP, report failing paths).

5 / 5

Progressive Disclosure

Well-organized into Setup/Interaction/Finish sections with no nested references, but it is a single ~130-line document whose dense native-host setup and error-handling detail could be split into a separate reference file.

4 / 5

Total

18

/

20

Passed

Description

53%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 states a clear capability and mechanism but omits any 'when to use' trigger guidance, which limits its completeness and trigger quality. It is reasonably distinct but would benefit from explicit use-when phrasing and natural keyword synonyms.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g., 'Use when the user asks to control, automate, or scrape Chrome / a browser').

Broaden natural keyword coverage with synonyms like 'browser', 'automate', 'web page', or 'scrape' alongside 'Chrome'.

List 1-2 more concrete actions (e.g., navigate tabs, fill forms, take screenshots) to lift specificity beyond the single generic verb 'Control'.

DimensionReasoningScore

Specificity

Names the domain (controlling Chrome) and a concrete action plus the mechanism ('through the existing persistent Node REPL and the Qwen Browser SDK'), but only a single generic action ('Control') with no broader coverage.

3 / 5

Completeness

The 'what' is clear (control Chrome via Node REPL + Qwen Browser SDK), but there is no 'Use when...' or equivalent trigger guidance, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

'Chrome' is a natural term users would say, but the rest (Node REPL, Qwen Browser SDK) is technical jargon and common variations like 'browser', 'automate', or 'scrape' are absent.

3 / 5

Distinctiveness Conflict Risk

Browser automation through this specific SDK is a clear, mostly distinct niche with only minor overlap risk against generic browser/web skills; not a 5 because no explicit trigger phrases delineate it.

4 / 5

Total

13

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
QwenLM/qwen-code
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.