playwright-test

Write a playwright test, make sure it runs, and is not flaky.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

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

The content is concise, highly actionable, and structured as a clear workflow with explicit validation and feedback loops for flakiness. Its only mild weakness is progressive disclosure, which relies on a single external README reference rather than a structured bundle.

Dimension	Reasoning	Score
Conciseness	The body is lean: it does not explain what Playwright is, offloads best practices to @playwright/README.md, and every line provides concrete instruction, matching the lean-and-efficient anchor at 5.	5 / 5
Actionability	Provides fully executable commands (the pnpm playwright invocation with BASE_URL, --retries 0, --workers 3, and --repeat-each 10) plus specific MCP tool names, fitting the copy-paste-ready anchor at 5.	5 / 5
Workflow Clarity	A clear four-step sequence (Plan, Implement, Ensure no flaky, Report) with an explicit validation checkpoint (--repeat-each 10) and feedback loops ('go back to Step 2', 'do not proceed until every run passes'), matching the explicit-validation anchor at 5.	5 / 5
Progressive Disclosure	Body is well-organized into clear sections and points one level deep to @playwright/README.md for best practices; it is not a 5 because there is only a single external reference rather than a clearly organized multi-file disclosure structure (no references/scripts/assets bundle dirs exist).	4 / 5
	Total	19 / 20 Passed

Description

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

The description clearly states what the skill does in a third-person imperative voice with relevant trigger terms, but it omits any explicit 'when to use' guidance and has limited keyword coverage. Adding a 'Use when...' clause and synonyms (e2e, end-to-end) would raise completeness and trigger term quality.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when writing or debugging Playwright (e2e) tests for a feature.'

Include natural synonyms and variations users say, such as 'end-to-end test', 'e2e test', 'flaky test', or 'browser test', to improve trigger term coverage.

Optionally name more concrete actions (e.g., plan, implement, run, and de-flake tests) to push specificity from 3 to 4-5.

Dimension	Reasoning	Score
Specificity	Names the domain ('playwright test') and two concrete outcomes ('make sure it runs', 'not flaky'), matching the 1-2 concrete actions anchor; it does not list several specific actions so it stays at 3 rather than 4.	3 / 5
Completeness	It has a clear 'what' (write a playwright test that runs and is not flaky) but no 'when'/'Use when...' clause, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural keywords 'playwright test' and 'flaky' that users would say, but lacks common variations like 'e2e test', 'end-to-end', or file extensions, fitting the missing-synonyms anchor at 3.	3 / 5
Distinctiveness Conflict Risk	'Playwright test' is a distinct niche with low overlap risk versus other skills, but it lacks explicit trigger phrases that would fully disambiguate, so it sits at 4 rather than 5.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: PostHog/posthog
Path: .agents/skills/playwright-test/SKILL.md
Commit: 6fca5f8

Reviewed: 3 days 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.