CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/playwright-testing

Authors and remediates Playwright E2E tests across Chromium, Firefox, WebKit - `npm init playwright@latest` scaffolding, `playwright.config.ts` browser projects, accessibility-first locators (`getByRole`/`getByLabelText`) to replace brittle CSS selectors, web-first assertions to eliminate `waitForTimeout` flakiness, Page Object pattern, trace viewer debugging, sharded parallel execution with merged HTML reporting, mobile-web emulation via the `devices` catalog (viewport / DPR / touch per-device projects), the cross-browser matrix with branded channels (chrome / msedge) in references/browser-matrix.md, and GitHub Actions CI integration. Use for new test authoring, flakiness remediation, mobile-breakpoint regression, cross-browser matrix setup, and CI setup; for reviewing codegen output specifically, use a dedicated codegen-review pass.

91

Quality

91%

Does it follow best practices?

Impact

Average score across 10 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

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

A tight, highly actionable skill body with executable code throughout and clean progressive disclosure into two real reference files. The main improvement would be adding a couple of explicit validation checkpoints (e.g. confirm the scaffolded example spec runs, assert the report artifact) inside the main workflow.

Suggestions

Add an explicit validation checkpoint after Step 1 (e.g. run the scaffolded example.spec.ts and assert it passes before authoring new tests) so the workflow has a built-in feedback loop.

Surface one short 'verify the run' checkpoint in Step 8/9 (assert the playwright-report artifact exists before counting CI green) rather than relying solely on the browser-matrix reference for verification guidance.

Consider dropping or shortening one of the pw-intro blockquotes in the Overview to tighten the already-efficient body further.

DimensionReasoningScore

Conciseness

Lean, action-oriented body with minimal preamble and no generic 'what is a browser' padding; the two short pw-intro blockquotes and the When-to-use list are the main trimmable framing, keeping it just shy of fully lean.

4 / 5

Actionability

Fully copy-paste-ready throughout: scaffold command, complete TypeScript spec, Page Object class, full playwright.config.ts, run/trace/shard commands, and a complete GitHub Actions YAML covering the common cases.

5 / 5

Workflow Clarity

Clear ordered Steps 1-9 with an anti-patterns table tying fixes back to steps, but the main body lacks explicit validation checkpoints (those live in the references), leaving minor validation gaps.

4 / 5

Progressive Disclosure

A well-organized overview that splits detail into two real, one-level-deep reference files (browser-matrix.md, mobile-emulation.md), each clearly signaled inline with a one-line description of its contents and easy navigation.

5 / 5

Total

18

/

20

Passed

Description

92%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, specific, third-person description that clearly states capabilities and explicit use-when triggers with concrete carve-outs. Its only weakness is a slightly jargon-heavy trigger surface that could include more natural user-voice synonyms.

Suggestions

Add a couple of plain-language synonyms to the trigger clause (e.g., 'end-to-end tests', 'Playwright test suite', 'browser automation') so the description matches how users actually phrase the request.

Consider trimming one or two of the most tool-internal tokens (e.g. 'merged HTML reporting') in the capabilities list to keep the description readable without losing specificity.

DimensionReasoningScore

Specificity

Lists many concrete capabilities (scaffolding, accessibility-first locators to replace CSS selectors, web-first assertions to eliminate waitForTimeout flakiness, sharded parallel execution, mobile-web emulation, branded-channel matrix, CI integration) with comprehensive coverage and no meaningful gaps.

5 / 5

Completeness

Explicitly answers both what (the long capabilities sentence) and when ('Use for ...' with concrete triggers), plus a carve-out directing codegen review elsewhere.

5 / 5

Trigger Term Quality

Includes natural trigger phrases ('new test authoring', 'flakiness remediation', 'mobile-breakpoint regression', 'cross-browser matrix setup', 'CI setup') alongside tool-specific tokens, though the density leans technical rather than covering the full spread of user-voice synonyms.

4 / 5

Distinctiveness Conflict Risk

Playwright-specific niche with named tooling and explicit carve-outs (codegen-review pass, Selenium migration) gives clear distinct triggers and minimal conflict risk.

5 / 5

Total

19

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents