playwright-testing-skill

Set up Playwright 1.49+ with TypeScript for E2E testing using page object model, fixtures, test.describe/test blocks, assertions, selectors, network mocking, CI configuration, and trace viewer.

Quality

80%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./testing/playwright-testing-skill/SKILL.md

Quality

Content

92%

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

This is a high-quality, comprehensive Playwright skill that provides excellent actionable guidance with complete, executable code examples. The content is well-structured and assumes Claude's competence without over-explaining. The main weakness is that the content is quite long and could benefit from progressive disclosure by splitting detailed patterns into separate reference files.

Suggestions

Consider splitting detailed patterns (page objects, network mocking, CI configuration) into separate reference files (e.g., PATTERNS.md, CI.md) with clear links from the main skill

Add a brief 'Quick Start' section at the top with just the scaffold command and minimal test example before diving into the full project structure

Dimension	Reasoning	Score
Conciseness	The skill is lean and efficient, providing executable code examples without explaining basic concepts Claude already knows. Every section serves a purpose with no padding or unnecessary explanations about what Playwright is or how testing works.	3 / 3
Actionability	Fully executable TypeScript code throughout with complete, copy-paste ready examples for config, page objects, fixtures, test specs, network mocking, and CLI commands. All code is real, not pseudocode.	3 / 3
Workflow Clarity	Clear project structure with logical organization, explicit setup flow (auth setup project runs before test projects via dependencies), and well-sequenced patterns from config to page objects to fixtures to specs. The auth flow includes validation (waitForURL, expect visibility).	3 / 3
Progressive Disclosure	Content is well-organized with clear sections, but it's a monolithic file (~350 lines) that could benefit from splitting detailed patterns (page objects, network mocking, CI setup) into separate reference files. The Integration Notes section mentions other skills but doesn't link to separate detailed docs.	2 / 3
	Total	11 / 12 Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description excels at specificity and distinctiveness by naming concrete Playwright features and specifying the version. However, it lacks an explicit 'Use when...' clause and could benefit from more natural trigger terms that users might say when needing E2E testing help.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'Use when setting up browser automation, end-to-end tests, or when the user mentions Playwright, E2E, or automated UI testing.'

Include common user-facing synonyms like 'browser testing', 'end-to-end tests', 'automated testing', 'UI tests' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'page object model, fixtures, test.describe/test blocks, assertions, selectors, network mocking, CI configuration, and trace viewer' - these are all concrete, specific capabilities.	3 / 3
Completeness	Clearly answers 'what' (set up Playwright with various features), but lacks an explicit 'Use when...' clause or trigger guidance. The 'when' is only implied through the technical terms.	2 / 3
Trigger Term Quality	Includes good technical terms like 'Playwright', 'TypeScript', 'E2E testing', but missing common user variations like 'end-to-end tests', 'browser testing', 'automated testing', or 'integration tests' that users might naturally say.	2 / 3
Distinctiveness Conflict Risk	Very specific niche with 'Playwright 1.49+ with TypeScript' - unlikely to conflict with other testing frameworks (Cypress, Jest, etc.) or general TypeScript skills due to the explicit tool and version specification.	3 / 3
	Total	10 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: achreftlili/deep-dev-skills
Commit: 181fcbc

Reviewed: 4 months ago

Table of Contents

Discovery Implementation Validation

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.