CtrlK
BlogDocsLog inGet started
Tessl Logo

browser-automation

Use when the user asks to automate browser tasks, scrape websites, fill forms, capture screenshots, extract structured data from web pages, or build web automation workflows. NOT for testing — use playwright-pro for that.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

66%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, actionable skill body with strong progressive disclosure to real reference and script files. It loses points on conciseness (restating familiar concepts) and workflow clarity (missing explicit validation/retry checkpoints in batch scraping workflows).

Suggestions

Trim the 'Why Playwright over Selenium or Puppeteer' rationale and selector-priority basics — Claude already knows these; keep only the skill-specific guidance.

Add explicit validation checkpoints to the pagination and download workflows (e.g., verify page count vs. expected, assert download completed and file is non-empty, retry-on-empty with backoff).

Consolidate the eight anti-pattern entries into a tighter checklist; several (hardcoded waits, no cleanup) overlap with guidance already implied by the competency sections.

DimensionReasoningScore

Conciseness

The body is detailed and largely useful, but the 8 competency sections plus 3 workflows and 8 anti-patterns restate knowledge Claude already has (e.g. why Playwright beats Selenium, selector reliability basics), adding padding that could be tightened.

3 / 5

Actionability

Three complete executable async Python workflows and inline code snippets for screenshots, storage state, and waiting give mostly copy-paste-ready guidance, with only minor gaps left to the referenced files.

4 / 5

Workflow Clarity

Workflows list clear numbered steps, but the batch/scraping workflows (50+ page scrape, downloads) lack explicit validation checkpoints or retry-on-failure feedback loops, which the rubric caps at 3 for batch operations.

3 / 5

Progressive Disclosure

SKILL.md is a well-organized overview that signals one-level-deep references to real bundle files (data_extraction_recipes.md, playwright_browser_api.md, anti_detection_patterns.md) and lists scripts in a reference table, making navigation easy.

5 / 5

Total

15

/

20

Passed

Description

100%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, well-crafted description that concretely enumerates capabilities, uses natural trigger phrasing, and explicitly disambiguates from the testing skill via a clear NOT-for clause. It cleanly answers both what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'automate browser tasks, scrape websites, fill forms, capture screenshots, extract structured data from web pages, or build web automation workflows' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both 'what' (the enumerated actions) and 'when' ('Use when the user asks to...'), with concrete trigger phrases plus a clear negative boundary ('NOT for testing').

5 / 5

Trigger Term Quality

Uses natural user-facing phrasing ('asks to automate browser tasks, scrape websites, fill forms, capture screenshots') that mirrors what a user would actually say, with strong synonym coverage.

5 / 5

Distinctiveness Conflict Risk

The explicit 'NOT for testing — use playwright-pro for that' carve-out establishes a clear niche and minimizes conflict with the closely related testing skill.

5 / 5

Total

20

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
alirezarezvani/claude-skills
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.