CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-browser

Browser automation via agent-browser CLI. Use when the user needs to navigate websites, fill forms, click buttons, take screenshots, extract data, or test web apps.

78

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is a tight, executable CLI reference with a well-sequenced core workflow, an explicit re-snapshot validation loop, and clean section navigation. It avoids conceptual padding and stays copy-paste ready throughout.

DimensionReasoningScore

Conciseness

A lean command reference with one-line intros and inline comments; it assumes Claude's competence and never explains what a browser or CDP is, so every token earns its place.

3 / 3

Actionability

Commands are fully executable and copy-paste ready (e.g. `agent-browser fill @e1 "user@example.com"`, `agent-browser wait --load networkidle`), with concrete worked examples rather than pseudocode.

3 / 3

Workflow Clarity

The numbered Core Workflow has an explicit feedback checkpoint ("Re-snapshot after any navigation or DOM change — refs are invalidated") plus a pre-flight verification step ("verify the tool is available by running `which agent-browser`"), giving a clear sequence with validation.

3 / 3

Progressive Disclosure

No bundle files exist, so the self-contained body is judged on organization; clear sections (Core Workflow, Commands, Authentication, Iframes, Parallel Sessions, JS Eval, Cleanup) provide easy navigation with no nested references.

3 / 3

Total

12

/

12

Passed

Description

100%

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 concise, third-person, and explicitly pairs a concrete capability list with a natural-language "Use when" trigger. It cleanly satisfies all four dimensions without padding or over-claiming.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "navigate websites, fill forms, click buttons, take screenshots, extract data, or test web apps" — matching the multi-action anchor rather than the single-domain level 2.

3 / 3

Completeness

Explicitly states what ("Browser automation via agent-browser CLI") and when ("Use when the user needs to navigate websites..."), satisfying both halves with an explicit trigger clause.

3 / 3

Trigger Term Quality

Natural phrasing a user would actually say ("navigate websites", "fill forms", "take screenshots", "test web apps"); good coverage, not jargon, so it clears the level-2 "some relevant keywords" bar.

3 / 3

Distinctiveness Conflict Risk

Browser automation is a clear, narrow niche with distinct triggers unlikely to fire for unrelated skills, matching the "clear niche with distinct triggers" anchor.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
sipeed/picoclaw
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.