CtrlK
BlogDocsLog inGet started
Tessl Logo

playwright-automation

Browser automation via Playwright for web testing, screenshots, form filling, scraping, and verification. Use when tasks require navigating websites, interacting with web pages, or testing web applications.

68

Quality

81%

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

75%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, code-heavy skill body that is executable and easy to navigate. It stays lean and covers the common Playwright patterns, with only minor gaps in consistency and validation guidance.

Suggestions

Resolve the module-style inconsistency (use ESM imports throughout, replacing the `require('playwright')` in the device-emulation example).

Replace the deprecated `page.waitForNavigation()` with `page.waitForURL()` and add a brief validate-on-failure note to the Workflow Loop.

Trim the redundant opening sentence that restates the frontmatter description.

DimensionReasoningScore

Conciseness

The body is lean and mostly code with minimal prose, assuming Claude's competence; the opening line partially restates the description and a few tips could be trimmed.

4 / 5

Actionability

Provides concrete, mostly copy-paste-ready TypeScript examples across navigation, interaction, screenshots, waiting, forms, network interception, and emulation; minor gaps include the mixed require/import and deprecated waitForNavigation.

4 / 5

Workflow Clarity

The Workflow Loop gives a clear five-step sequence with an 'Evaluate' feedback checkpoint, though explicit validation/error-recovery guidance for failed runs is light.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections (When to Use, Approach Selection, Core Workflow, Key Patterns, Workflow Loop, Tips) with no nested references; slightly over the simple-skill line so not a full 5.

4 / 5

Total

16

/

20

Passed

Description

88%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, third-person description that names concrete capabilities and gives explicit trigger guidance. It is specific, actionable, and clearly signals when to invoke the skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'web testing, screenshots, form filling, scraping, and verification' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (browser automation via Playwright for the listed actions) and 'when' ('Use when tasks require navigating websites, interacting with web pages, or testing web applications') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases users would say ('navigating websites', 'interacting with web pages', 'testing web applications', 'screenshots', 'scraping') are present, but a few synonyms/variations are missing.

4 / 5

Distinctiveness Conflict Risk

The Playwright-specific framing carves a clear niche with minimal conflict risk, though it could still slightly overlap with generic web-testing or browser-automation skills.

4 / 5

Total

18

/

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
ArabelaTso/Skills-4-SE
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.