CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agent-browser

Browse the web for any task — research topics, read articles, interact with web apps, fill forms, take screenshots, extract data, and test web pages. Use whenever a browser would be useful, not just when the user explicitly asks.

Quality

87%

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

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.

Highly actionable, executable reference with a clear workflow and an unusually strong section on bounded waits with explicit failure recovery. The main gaps are triplicated command listings and no offloading of the full command catalog to a reference file.

Suggestions

Collapse the duplication between Quick start, Core workflow, and the Commands sections into one listing so each command appears once.

Move the exhaustive command catalog (navigation/get/cookies/storage variants) into a references file and keep only the high-frequency commands plus the bounded-wait guidance in SKILL.md.

DimensionReasoningScore

Conciseness

The command tables are dense and assume Claude's competence (no library comparisons or concept padding), but the same commands appear three times across Quick start, Core workflow, and the Commands section, which is noticeable redundancy.

4 / 5

Actionability

Every command is copy-paste ready with inline comments (e.g. "agent-browser fill @e2 \"text\""), the bounded-wait example is a complete executable script, and the form and data-extraction examples cover the common cases.

5 / 5

Workflow Clarity

The numbered core workflow ends with "Re-snapshot after navigation or significant DOM changes", and the bounded-wait section adds an explicit feedback loop: on TIMEOUT, snapshot the page, report, and never re-enter an unbounded wait.

5 / 5

Progressive Disclosure

Sections are well-organized with clear headers per command group, but the full CLI command catalog is inlined in one ~190-line file with no reference split, and the doc exceeds the simple-skill threshold where inline-only structure would score 5.

4 / 5

Total

18

/

20

Passed

Description

80%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 with concrete, comprehensive capabilities and explicit use-when guidance in third person. Its main weaknesses are a generic trigger heuristic instead of concrete trigger phrases and slight overlap with search/research skills.

Suggestions

Replace the generic heuristic with concrete trigger phrases, e.g. "Use when the user asks to research a topic, fill out a web form, take a screenshot of a page, or extract data from a website".

Add natural synonyms users say, such as "web scraping", "visit/open a website", or "log in to a site", to broaden trigger coverage.

Sharpen the boundary with search skills, e.g. noting this skill is for interacting with pages in a real browser rather than just fetching search results.

DimensionReasoningScore

Specificity

"research topics, read articles, interact with web apps, fill forms, take screenshots, extract data, and test web pages" lists multiple concrete actions with comprehensive coverage of the browser-automation domain.

5 / 5

Completeness

Both a clear "what" (the action list) and an explicit "when" ("Use whenever a browser would be useful") are present, but the trigger guidance is a general heuristic rather than the concrete trigger phrases of the top anchor.

4 / 5

Trigger Term Quality

Natural phrases like "browse the web", "fill forms", "take screenshots", and "extract data" give good keyword coverage, but common synonyms such as "web scraping" or "visit a website" are missing.

4 / 5

Distinctiveness Conflict Risk

"Browse the web" carves a distinct browser-automation niche, but "research topics, read articles" and the deliberately broad "whenever a browser would be useful" create minor overlap risk with web-search/fetch skills.

4 / 5

Total

17

/

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

nanocoai/nanoclaw

Path

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