CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

browser-use

Use this skill when the user asks the agent to open, browse, inspect, extract content from, click through, fill forms on, screenshot, or verify a web page with a browser. Also use it for MoviePilot scenarios that need browser interaction, such as checking a site page, confirming a JavaScript-rendered result, testing login state, capturing visible errors, or updating and validating tracker site cookies.

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

77%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 delivers highly actionable, well-sequenced workflows with genuine validation and error-recovery loops — the strongest part of the skill. Its weaknesses are repetition and host-implementation detail that inflate token cost, and a monolithic single-file layout that inlines reference-grade material instead of splitting it out.

Suggestions

Deduplicate the session-bound captcha guidance (stated in the `view_image` tool bullet, captcha step 2, and step 4) into a single authoritative statement and trim host implementation details (60-second scan cadence, TaskRegistry rollback mechanics) to the one behavioral rule the agent needs: re-open and re-verify after long waits, close sessions explicitly.

Move the detailed MoviePilot site workflows — especially the graphic-captcha login ladder and the session idle policy — into a references/ file, keeping SKILL.md as a concise overview with one-level-deep pointers per the progressive-disclosure model.

Add Chinese trigger phrases (e.g., 打开网页, 截图, 登录失效, 更新Cookie) to the description and When To Use section, since the skill's own Examples show its users prompting in Chinese.

DimensionReasoningScore

Conciseness

The body is mostly efficient, command-centric, and free of explanations of concepts Claude already knows, but it needs tightening beyond "minor" trimming: session-bound captcha guidance is repeated across the Tools section and steps 2 and 4 of the captcha workflow, and host implementation details ("宿主在正常及安全模式下每 60 秒扫描一次", TaskRegistry scan/rollback mechanics) exceed what the agent needs to act on. It is well above 2, since there is no padded library-tutorial prose, but the repetition and implementation detail keep it below 4.

3 / 5

Actionability

Nearly every instruction is a copy-paste-ready command — `browse_webpage action="goto" url="https://example.com"`, `click_ref`/`fill_ref`/`select_ref` usage, an executable `evaluate` script, and full `moviepilot_api operation_id=...` calls — and the Examples section covers the common cases end-to-end. This matches the 5 anchor and exceeds 4 because placeholders only appear where values are inherently user-supplied (credentials, refs).

5 / 5

Workflow Clarity

Multi-step processes are explicitly sequenced with validation checkpoints and feedback loops: the core "navigate → observe → one small action → verify" loop, the site diagnosis workflow that re-runs `site.test` to confirm the fix, and the captcha workflow's recovery path (OCR fail → visual recognition → refresh once → manual input) with a hard three-attempt limit and post-rejection re-inspection. This matches the 5 anchor; 4 would require some checkpoints to be merely implied, which they are not.

5 / 5

Progressive Disclosure

Section headers are clear and flat, but the entire skill is a single ~310-line file with no bundle files, and roughly 120 lines of specialized detail (the captcha login edge-case ladder, the session idle/TaskRegistry lifecycle policy) are inlined where the rubric expects them in one-level-deep reference files. This fits the 3 anchor ("content that should be separate is inline") better than 4 — the gap is more than minor — while remaining above 2 since structure and navigation within the file are good.

3 / 5

Total

16

/

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: concrete action verbs, an explicit double "use when" trigger clause, and a clearly bounded browser/MoviePilot niche. The only weakness is trigger-term coverage that stops short of full synonym coverage and omits the Chinese phrases its actual users would say.

DimensionReasoningScore

Specificity

The description enumerates many concrete actions — "open, browse, inspect, extract content from, click through, fill forms on, screenshot, or verify a web page" plus "checking a site page, confirming a JavaScript-rendered result, testing login state, capturing visible errors, or updating and validating tracker site cookies" — giving comprehensive, not just partial, coverage. It exceeds the 4 anchor ("several specific actions; minor gaps") because the action list spans navigation, interaction, extraction, and verification with essentially no gaps.

5 / 5

Completeness

Both halves are explicit: the "what" is the enumerated set of browser actions, and the "when" is stated twice — "Use this skill when the user asks the agent to open, browse, ... a web page" and "Also use it for MoviePilot scenarios that need browser interaction, such as ...". This matches the 5 anchor (clear, explicit what AND when with concrete trigger phrases) and exceeds 4, where the "when" would be less specific.

5 / 5

Trigger Term Quality

Natural trigger phrases are well covered ("open", "screenshot", "fill forms", "capturing visible errors", "testing login state", "update ... cookies"), matching the 4 anchor of good keyword coverage. It falls short of the 5 anchor because common variations like "visit" or "look at this page" are absent and — despite the skill's Examples being Chinese-language MoviePilot prompts — no Chinese trigger terms appear; it is clearly above 3 since far more than "some relevant keywords" is present.

4 / 5

Distinctiveness Conflict Risk

The niche is clear — browser-based page interaction plus MoviePilot tracker-site/cookie workflows — with distinct triggers unlikely to fire for unrelated skills. Minor overlap with a plain web-search skill exists, but the "with a browser" framing and MoviePilot-specific scenarios keep conflict risk minimal, fitting the 5 anchor better than 4.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

jxxghp/MoviePilot

Path

skills/browser-use/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.