CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

86

Quality

84%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Discovery

92%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that clearly communicates capabilities and provides excellent trigger coverage with natural user phrases. The 'Use when' and 'Triggers include' sections make it highly actionable for skill selection. The only minor weakness is potential overlap with other web-related skills like dedicated scrapers or testing tools, though the browser automation framing helps mitigate this.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, and automating browser tasks.

3 / 3

Completeness

Clearly answers both 'what' (browser automation CLI for AI agents with specific capabilities listed) and 'when' (explicit 'Use when' clause plus a 'Triggers include' section with concrete user phrases).

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would say: 'open a website', 'fill out a form', 'click a button', 'take a screenshot', 'scrape data from a page', 'test this web app', 'login to a site', 'automate browser actions'. These are highly natural phrases.

3 / 3

Distinctiveness Conflict Risk

While browser automation is a fairly specific niche, terms like 'extracting data', 'filling forms', and 'testing web apps' could overlap with web scraping tools, form-processing skills, or testing frameworks. The description could be more explicit about what distinguishes it (e.g., it's a CLI tool, uses a specific browser engine).

2 / 3

Total

11

/

12

Passed

Implementation

77%

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

This is a highly actionable and well-structured skill with excellent concrete examples throughout. Its main weakness is length — at 400+ lines with redundant authentication sections and an inline command reference that duplicates a referenced file, it could be significantly more concise. The workflow clarity is strong with clear sequencing, validation steps (diff, re-snapshot), and explicit guidance on when to chain vs. separate commands.

Suggestions

Remove the redundant authentication examples in 'Common Patterns' since 'Handling Authentication' already covers all 5 options in detail, or consolidate into a single section with the recommended approach inline and others in references/authentication.md.

Move the 'Essential Commands' reference block to references/commands.md (which is already listed in the reference table) and keep only the most critical 5-6 commands inline.

Consolidate the viewport/device content which appears both in 'Essential Commands' and 'Common Patterns > Viewport & Responsive Testing' with overlapping information.

DimensionReasoningScore

Conciseness

The skill is quite long (~400+ lines) and covers many features comprehensively, but some sections are redundant (e.g., authentication is explained in both 'Handling Authentication' with 5 options AND repeated in 'Common Patterns' with overlapping examples). The viewport/device section also repeats information. However, it generally avoids explaining concepts Claude already knows and most content is command-focused rather than explanatory.

2 / 3

Actionability

Nearly every section provides concrete, copy-paste-ready bash commands with realistic arguments. The examples use specific URLs, element refs, and flags that make them immediately executable. Code blocks dominate over prose, and edge cases like shell quoting in eval are addressed with specific solutions.

3 / 3

Workflow Clarity

The core workflow is clearly sequenced (navigate → snapshot → interact → re-snapshot) with explicit validation patterns. The 'Ref Lifecycle' section serves as a critical validation checkpoint, the diff section provides verification workflows, and the session cleanup section addresses error recovery. The 'when to chain' guidance helps Claude make correct sequencing decisions.

3 / 3

Progressive Disclosure

The skill has a well-organized reference table pointing to 7 deep-dive documents and 3 templates, which is good progressive disclosure. However, the main SKILL.md itself is very long with substantial inline content that could be offloaded — particularly the 5 authentication options, the extensive command reference section, and multiple common patterns. The command reference alone could be in a separate file since references/commands.md is already listed. No bundle files were provided to verify the referenced paths exist.

2 / 3

Total

10

/

12

Passed

Validation

81%

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

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (646 lines); consider splitting into references/ and linking

Warning

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

9

/

11

Passed

Repository
databricks/devhub
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.