CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

playwright-best-practices

Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions, multi-tab/popup flows, mobile/responsive layouts, touch gestures, GraphQL, error handling, offline mode, multi-user collaboration, third-party services (payments, email verification), console error monitoring, global setup/teardown, test annotations (skip, fixme, slow), test tags (@smoke, @fast, @critical, filtering with --grep), project dependencies, security testing (XSS, CSRF, auth), performance budgets (Web Vitals, Lighthouse), iframes, component testing, canvas/WebGL, service workers/PWA, test coverage, i18n/localization, Electron apps, or browser extension testing. Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary dispatcher skill: the body stays lean as a routing index with one-level-deep references per activity, and its single multi-step workflow (the validation loop) has explicit checkpoints and retry feedback. Its main weakness is token efficiency — the activity tables and the decision tree duplicate the same mapping, roughly doubling the navigation content.

Suggestions

Cut the duplication between the Activity-Based Reference Guide tables and the Quick Decision Tree — both encode the same activity→reference mapping (e.g., flaky-test debugging routes appear in both); keeping the tables and deleting the tree would remove ~100 lines with no information loss.

Remove the intro sentence ("This skill provides comprehensive guidance for all aspects of Playwright test development…") since it restates the frontmatter description without adding routing value.

Consolidate rows that repeatedly point to the same single file (e.g., four Mobile & Responsive rows all routing to mobile-testing.md) into grouped rows to reduce table overhead.

DimensionReasoningScore

Conciseness

There is no over-explanation of concepts Claude already knows, but the "Activity-Based Reference Guide" tables and the "Quick Decision Tree" encode the exact same activity→reference mapping twice (e.g., "Flaky test investigation → debugging/flaky-tests.md" appears in both), roughly doubling the body's token cost; the intro line also restates the frontmatter.

3 / 5

Actionability

The validation loop gives copy-paste-ready commands ("npx playwright test --reporter=list", "npx playwright show-trace", "--repeat-each=5") and every activity row points to a specific reference file, but the body itself contains no executable Playwright test-writing guidance — it is entirely delegated to the referenced files.

4 / 5

Workflow Clarity

The "Test Validation Loop" is a clear sequence with an explicit validation gate and feedback loop: run tests, review error output and trace on failure, fix and re-run, "Only proceed when all tests pass", then "Run multiple times" with --repeat-each=5 — matching the checkpoint-and-recovery anchor.

5 / 5

Progressive Disclosure

The body is a pure overview: all detail lives in one-level-deep, clearly signaled reference links organized by activity category with "When to use" guidance per section (e.g., "**Fixing flaky tests** | flaky-tests.md, debugging.md, assertions-waiting.md"), making navigation easy. No bundle files were present in references/ to verify the link targets, so structure is scored on the references as written.

5 / 5

Total

17

/

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 dense, highly explicit routing description: every clause is a distinct concrete trigger for the Playwright testing domain, with both what (scope sentence) and when ("Use when…") clearly answered. The only nitpick is sheer length (~1,000 characters), but it is trigger-dense rather than padded, so no dimension is penalized.

DimensionReasoningScore

Specificity

The description lists many concrete actions — "writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs" — with comprehensive coverage of the domain and no vague filler.

5 / 5

Completeness

The "when" is explicit via the opening "Use when writing Playwright tests…" trigger clause, and the "what" is explicitly stated as "Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing" plus the enumerated activity list — both questions answered with concrete trigger phrases.

5 / 5

Trigger Term Quality

It contains the natural terms users would actually say for this domain — "flaky tests", "Page Object Model", "CI/CD", "OAuth", "WebSockets", "GraphQL", "axe-core", "iframes", "PWA", "Electron apps", "--grep", "@smoke, @fast, @critical" — comprehensive coverage including synonyms and tool-specific keywords.

5 / 5

Distinctiveness Conflict Risk

"Playwright" is named in the first clause and the closing scope sentence, anchoring the skill to a clear niche with distinct triggers; overlap risk is limited to at most closely adjacent web-testing skills.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 132 missing

Warning

Total

15

/

16

Passed

Repository

BigSimmo/PsychSift

Path

.claude/cloud-profile/skills/playwright-best-practices/SKILL.md

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.