CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-browser

Browser automation CLI for AI agents. Use when the user needs to inspect, test, or automate browser behavior: navigating pages, filling forms, clicking buttons, taking screenshots, extracting page data, reading selected OpenDesign browser-tab context, testing web apps, dogfooding OpenDesign previews, QA, bug hunts, or reviewing app quality. Prefer local OpenDesign preview URLs unless the user explicitly asks for external browsing.

74

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

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.

A well-structured, highly actionable skill body with clear sequencing, validation, and error recovery. The main weakness is duplicated Chrome/CDP startup logic across two sections, which slightly hurts conciseness and organization.

Suggestions

Factor the shared Chrome-launch + CDP-polling block into a single reusable snippet and reference it from both 'CDP Startup Contract' and 'OpenDesign Smoke Path' to remove duplication.

Tighten the prose in 'Browser Context Extraction' and 'CDP Startup Contract' to drop explanatory sentences that restate what the commands already show.

Consider moving the full specialized-guide catalog into a short reference table so the 'Specialized Upstream Guides' section signals navigation without listing every temp-file redirect inline.

DimensionReasoningScore

Conciseness

Mostly lean, command-driven guidance that assumes competence, but the Chrome launch + CDP polling block is duplicated between 'CDP Startup Contract' and 'OpenDesign Smoke Path' and a few explanatory passages could be trimmed.

4 / 5

Actionability

Fully executable, copy-paste-ready bash throughout — install check, CDP attach sequence, connect/open/snapshot/screenshot commands — covering the common cases concretely.

5 / 5

Workflow Clarity

An 11-step Workflow with explicit validation checkpoints (CLI verify, CDP polling, expected success criteria) and error-recovery feedback loops (Chrome crash → report; CDP unavailable → ask user to launch manually).

5 / 5

Progressive Disclosure

Well-organized into single-purpose sections with one-level-deep, on-demand upstream guides loaded to temp files; no bundle files exist, and the duplicated CDP startup script is a minor organization gap.

4 / 5

Total

18

/

20

Passed

Description

96%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 that clearly states capability and trigger conditions with concrete, natural-language phrases and third-person voice. Minor overlap risk from a few generic trigger terms keeps distinctiveness just below the top anchor.

DimensionReasoningScore

Specificity

Lists many concrete actions — 'navigating pages, filling forms, clicking buttons, taking screenshots, extracting page data' plus QA/bug hunts — giving comprehensive coverage of what the CLI does.

5 / 5

Completeness

Explicitly answers what ('Browser automation CLI for AI agents') and when ('Use when the user needs to inspect, test, or automate browser behavior...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural user phrases abound ('take a screenshot', 'extract logo', 'click a button', 'fill out a form', 'scrape page', 'QA', 'bug hunt') with synonyms covered across both the description and triggers field.

5 / 5

Distinctiveness Conflict Risk

The OpenDesign-scoped, local-preview-first niche is fairly distinct, but generic triggers like 'open website' and 'scrape page' create minor overlap risk with general browser/scraping skills.

4 / 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.

Validation15 / 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
nexu-io/open-design
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.