CtrlK
BlogDocsLog inGet started
Tessl Logo

playwright-cli

Automate browser interactions, test web pages and work with Playwright tests.

54

Quality

60%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/playwright-cli/SKILL.md

The canonical home for this skill is playwright-cli in microsoft/playwright-cli

SKILL.md
Quality
Evals
Security

Quality

Content

87%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured, highly actionable skill that serves as an excellent command reference for playwright-cli browser automation. Its main strength is the comprehensive yet concise command catalog with real examples and good progressive disclosure to reference files. The primary weakness is the lack of validation/verification steps in workflows—examples show sequences of actions but never check outcomes or handle errors.

Suggestions

Add validation checkpoints to workflow examples, e.g., after form submission, verify the page navigated correctly or check for error messages in the snapshot before proceeding.

Include a brief troubleshooting or error recovery pattern, such as what to do when a click doesn't produce the expected result or when an element ref is stale.

DimensionReasoningScore

Conciseness

The content is lean and efficient throughout. It avoids explaining what Playwright is or how browsers work, instead jumping straight into commands and examples. Every section serves a clear purpose with no filler text.

3 / 3

Actionability

Every command is concrete and copy-paste ready with real bash examples. The skill provides specific command syntax, flags, and arguments rather than abstract descriptions. Examples like form submission and multi-tab workflows are fully executable.

3 / 3

Workflow Clarity

The examples show clear sequences (open → snapshot → interact → close), but there are no explicit validation checkpoints or error recovery steps. For browser automation involving form submissions and state changes, there's no guidance on verifying success or handling failures after actions.

2 / 3

Progressive Disclosure

The skill provides an excellent overview with a quick start, organized command reference sections, and clearly signaled one-level-deep references to 9 specific topic files at the bottom. Content is well-split between the overview and detailed reference files.

3 / 3

Total

11

/

12

Passed

Description

32%Scale 1-3

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 identifies the core domain (Playwright browser automation and testing) but lacks specificity in its listed capabilities and completely omits an explicit 'Use when...' clause. It would benefit from more concrete actions and natural trigger terms to help Claude reliably select this skill from a large pool.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about browser automation, end-to-end testing, Playwright scripts, or .spec.ts files.'

Include more natural trigger terms users would say, such as 'e2e tests', 'end-to-end testing', 'headless browser', 'UI testing', 'web scraping', 'browser scripts'.

List more specific concrete actions, e.g., 'Navigate pages, click elements, fill forms, capture screenshots, write and run Playwright test specs, handle assertions and selectors.'

DimensionReasoningScore

Specificity

Names the domain (browser automation, web testing, Playwright) and some actions ('automate browser interactions', 'test web pages', 'work with Playwright tests'), but the actions are somewhat general rather than listing specific concrete capabilities like 'click elements, fill forms, take screenshots, assert page content'.

2 / 3

Completeness

Describes what the skill does (automate browser interactions, test web pages, work with Playwright tests) but has no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric should cap completeness at 2, and the 'what' portion is also fairly thin, placing this closer to a 1.

1 / 3

Trigger Term Quality

Includes 'Playwright', 'browser', 'web pages', and 'tests' which are relevant keywords, but misses common variations users might say like 'e2e tests', 'end-to-end testing', 'browser automation', 'web scraping', 'headless browser', '.spec.ts', or 'UI testing'.

2 / 3

Distinctiveness Conflict Risk

Mentioning 'Playwright' specifically helps distinguish it from generic testing or browser skills, but 'automate browser interactions' and 'test web pages' are broad enough to potentially overlap with other web testing or automation skills like Selenium or Cypress-based ones.

2 / 3

Total

7

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
hefgi/dotfiles
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.