CtrlK
BlogDocsLog inGet started
Tessl Logo

playwright-testing

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.

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%

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

The body is a lean, well-organized routing layer with an excellent validation loop, scoring top marks on conciseness, actionability, and workflow clarity. Its single flaw is that the entire progressive-disclosure scheme points to bundle files that are not present, capping progressive_disclosure at 2.

Suggestions

Add the referenced bundle files under references/ (e.g. core/locators.md, testing-patterns/component-testing.md) or remove links to files that don't exist, so the navigation resolves to real content.

Verify every path in the activity tables and decision tree maps to an actual file; dangling links undermine the skill's otherwise strong disclosure structure.

Consider grouping the ~40-item frontmatter trigger list into a few readable clauses to reduce the run-on description's verbosity.

DimensionReasoningScore

Conciseness

The body is pure routing — activity tables and a decision tree with no concept explanation or filler — assuming Claude's competence and earning every token, matching the lean anchor.

3 / 3

Actionability

Provides concrete file paths per activity and real executable commands in the validation loop ('npx playwright test --reporter=list', 'npx playwright show-trace', '--repeat-each=5'), copy-paste ready rather than abstract.

3 / 3

Workflow Clarity

The 'Test Validation Loop' is a clear numbered sequence with an explicit validation checkpoint ('Only proceed when all tests pass') and a fix/re-run feedback loop, matching the validation-with-checkpoints anchor.

3 / 3

Progressive Disclosure

Structure is exemplary — activity tables and a decision tree give one-level-deep, clearly signaled navigation — but the referenced bundle files (core/locators.md, testing-patterns/*, etc.) do not exist in references/, scripts/, or assets/, so the disclosed paths are broken rather than real.

2 / 3

Total

11

/

12

Passed

Description

100%

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 is a comprehensive, well-triggered Playwright testing skill descriptor that hits every dimension's top anchor. Its one weakness is verbosity: the 'Use when' clause is a single ~40-item run-on sentence, which the guidelines caution against even though no dimension here directly penalizes length.

DimensionReasoningScore

Specificity

Names many concrete capabilities via gerund phrases — 'implementing Page Object Model', 'mocking APIs', 'handling authentication or OAuth', 'testing accessibility (axe-core)', 'canvas/WebGL', 'service workers/PWA' — paralleling the anchor's multi-action list.

3 / 3

Completeness

Explicitly answers both: an opening 'Use when writing Playwright tests...' trigger clause and a closing 'Covers E2E, component, API, visual...' summary of scope, satisfying the what-AND-when anchor.

3 / 3

Trigger Term Quality

Dense coverage of natural terms a user would say — 'flaky tests', 'Page Object Model', 'CI/CD', 'OAuth', 'axe-core', 'WebSockets', '@smoke, @fast, @critical', '--grep' — matching the good-coverage anchor.

3 / 3

Distinctiveness Conflict Risk

The Playwright-specific niche (POM, trace viewer, --grep tags, project dependencies) is distinct and unlikely to trigger for a non-Playwright skill.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 130 missing

Warning

Total

15

/

16

Passed

Repository
MODSetter/SurfSense
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.