CtrlK
BlogDocsLog inGet started
Tessl Logo

web-browser

Automate and interact with web pages through Chrome or Chromium using the Chrome DevTools Protocol (CDP): navigate, click, fill forms, inspect content, take screenshots, and debug console or network activity. Use when an agent needs a real browser. Prefer headless Chrome unless visible browser interaction is required.

80

Quality

100%

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

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 well-organized command reference: concise, fully actionable, and structured as an overview pointing one level deep to real bundle scripts. It assumes Claude's competence and adds only what is needed to drive the browser tooling.

DimensionReasoningScore

Conciseness

Lean throughout: no explanations of what a browser or CDP is, no library comparisons; each section is a command block plus one to three lines that all earn their place.

3 / 3

Actionability

Every command is executable and copy-paste ready with real flags shown (e.g. --headless, --new, --full-page, --device), and the eval examples include runnable JavaScript expressions.

3 / 3

Workflow Clarity

Each command is an unambiguous single action, and the "Quick Mobile Debug Flow" provides a clearly ordered multi-step recipe; no destructive or batch operations are present that would require validation checkpoints.

3 / 3

Progressive Disclosure

SKILL.md is a concise overview indexing one-level-deep script references, all of which exist in ./scripts/ (start.js, nav.js, eval.js, screenshot.js, pick.js, dismiss-cookies.js, emulate.js, watch.js, logs-tail.js, net-summary.js), with logic appropriately split into those scripts.

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 specific, complete, and distinct: it names concrete capabilities, includes an explicit Use-when trigger, and carves out a clear browser-automation niche. It avoids vague fluff and verbosity.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "navigate, click, fill forms, inspect content, take screenshots, and debug console or network activity" — grounded in the Chrome/Chromium + CDP mechanism, matching the anchor for several specific concrete actions.

3 / 3

Completeness

Explicitly answers both what (the action list and CDP mechanism) and when via the "Use when an agent needs a real browser" clause, satisfying the explicit-trigger requirement.

3 / 3

Trigger Term Quality

Covers natural user phrasing ("web pages," "real browser," "forms," "screenshots") alongside the technical CDP name, giving good coverage of terms a user would actually say when needing browser automation.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (real-browser automation via CDP) with a distinct "needs a real browser" trigger, making overlap with file or document skills unlikely.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mitsuhiko/agent-stuff
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.