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.

70

Quality

88%

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

93%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.

Excellent operational content: fully executable commands, non-obvious operational caveats, and a well-organized overview that delegates implementation to the bundled scripts. The only improvement would be explicit verification steps between navigation and downstream actions like screenshots.

DimensionReasoningScore

Conciseness

The body is lean command blocks plus brief operational notes the agent could not infer (profile isolation, port-lock refusal, headless extension behavior); it never explains concepts Claude already knows and every section earns its tokens.

5 / 5

Actionability

Every section gives copy-paste-ready bash commands with flags and realistic arguments (nav, eval with an escaping caveat, screenshot options, dismiss-cookies), plus a complete end-to-end "Quick Mobile Debug Flow" covering common cases.

5 / 5

Workflow Clarity

Multi-step flows are clearly sequenced (start → nav → emulate → reload → dismiss → screenshot; stop/start for headless↔headed switching) with safety notes ("Stop before using --reset-profile", stop "never force-kills Chrome"), but there are no explicit load/verify checkpoints between steps, matching 'most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

The SKILL.md is a clean overview with one section per script, implementation lives in the verified scripts/ bundle, every referenced path resolves to a real file, and there are no nested or buried references.

5 / 5

Total

19

/

20

Passed

Description

78%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 names the domain, enumerates concrete capabilities, and includes an explicit use-when clause with sensible headless-by-default guidance. Its only weaknesses are slightly incomplete capability coverage and a 'when' clause that could name more concrete user-side triggers.

Suggestions

Add the remaining capabilities (device/mobile emulation, cookie-consent dismissal, console/network logging) to the action list so the description covers everything the skill provides.

Ground the 'Use when' clause in user-intent triggers, e.g. "Use when the user asks to open, click through, screenshot, or scrape a real website or needs JavaScript rendering that plain HTTP requests cannot handle."

Include one or two common synonyms such as "web scraping" or "browser automation" to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Lists six concrete actions ("navigate, click, fill forms, inspect content, take screenshots, and debug console or network activity") but omits capabilities the skill actually provides (device emulation, cookie-dialog dismissal, background logging), matching the 'several specific actions; minor gaps' anchor rather than comprehensive coverage.

4 / 5

Completeness

Explicitly answers both what (the action list) and when ("Use when an agent needs a real browser"), so it clears the missing-trigger cap of 3, but the 'when' clause is single-condition and agent-centric rather than grounded in concrete user-intent trigger phrases.

4 / 5

Trigger Term Quality

Good natural keyword coverage ("web pages", "Chrome", "Chromium", "fill forms", "take screenshots", "headless"), but common user phrasings such as "web scraping" or "browse a website" are missing, so it falls just short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

Clear niche of real-browser automation via CDP ("through Chrome or Chromium using the Chrome DevTools Protocol"), and "when an agent needs a real browser" cleanly distinguishes it from plain HTTP-fetch skills, giving minimal conflict risk.

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