CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agent-browser

Use the agent-browser CLI to exercise web interfaces, inspect rendered accessibility state, verify interactions, and capture screenshots. Use for browser-based UI testing and evidence collection. Do not use as a substitute for deterministic Playwright coverage when an automated regression test is the requested deliverable.

72

Quality

90%

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

92%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 compact skill body: a concrete verification loop with explicit validation and feedback steps, lean non-obvious guidance throughout, and appropriate deferral of version-sensitive syntax to the CLI's own docs. The only minor gap is that a few common command invocations (snapshot, wait) are named but not shown.

DimensionReasoningScore

Conciseness

The ~45-line body is lean with every token earning its place; it teaches only non-obvious operational knowledge ('References can become stale after navigation or a substantial DOM update', 'a completed screenshot command does not prove that the intended state was visible') with no filler or explanation of concepts Claude already knows.

5 / 5

Actionability

Provides mostly executable guidance: copy-paste commands ('agent-browser skills get core --full', the dev-bypass URL) and named subcommands ('agent-browser console', 'agent-browser errors', 'agent-browser network requests'). It falls short of fully copy-paste-ready coverage because snapshot and wait command syntax is deferred to the CLI's own docs rather than shown for common cases.

4 / 5

Workflow Clarity

The 7-step verification loop is clearly sequenced with explicit validation checkpoints (wait for state, re-snapshot, verify result/console/network), a feedback loop ('Check agent-browser console and agent-browser errors when the UI behaves unexpectedly'), and a pre-success gate ('Inspect the saved image before reporting success').

5 / 5

Progressive Disclosure

A single-purpose skill under 50 lines with no bundle files and no need for external references; it is well-organized into clear sections and appropriately defers version-sensitive command syntax one level deep to the CLI's version-matched instructions, satisfying the simple-skill exception.

5 / 5

Total

19

/

20

Passed

Description

83%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, specific description with concrete capabilities, an explicit use-for clause, and unusually good boundary guidance against the nearest competing tool (Playwright). The main weakness is trigger coverage: only one 'Use for' clause with no natural user-phrase variations or synonyms.

Suggestions

Add a few concrete user-mention triggers to the 'when' clause, e.g. 'Use when the user asks to test or click through a web UI, check rendered pages, take browser screenshots, or gather visual evidence of behavior'.

Include common synonyms for the domain such as 'E2E', 'end-to-end testing', or 'browser automation' so natural user phrasings match the trigger terms.

DimensionReasoningScore

Specificity

Lists four concrete, specific actions ('exercise web interfaces, inspect rendered accessibility state, verify interactions, and capture screenshots') with comprehensive coverage of the CLI's testing role, matching the top anchor rather than leaving minor gaps.

5 / 5

Completeness

Clearly answers 'what' with multiple concrete actions and has an explicit 'Use for browser-based UI testing and evidence collection' when-clause, but the trigger guidance is a single clause without concrete user-mention variations, so 'when' could be more explicit per the anchor-4 example.

4 / 5

Trigger Term Quality

Includes good natural keywords ('browser-based UI testing', 'evidence collection', 'screenshots', 'Playwright', 'regression test') but misses common user phrasings like 'test the app in the browser' or 'E2E', so it fits 'good keyword coverage; a few natural terms missing' rather than comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

Names a specific niche tool and includes explicit anti-conflict guidance ('Do not use as a substitute for deterministic Playwright coverage when an automated regression test is the requested deliverable'), giving it a clear niche with minimal conflict risk.

5 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

emdash-cms/emdash

Path

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