CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/playwright-snapshots

Authors Playwright `expect(page).toHaveScreenshot()` assertions, configures masks / clips / threshold / maxDiffPixels per test, manages the per-OS / per-browser snapshot directory, and runs the update flow with `--update-snapshots`. Use when the project ships self-hosted visual regression coverage in Playwright (no external snapshot service).

75

Quality

94%

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

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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

The body is concise and highly actionable with executable code, config, and CI throughout. Its weaknesses are a missing explicit validation feedback loop around the destructive `--update-snapshots` update and an all-inline structure with no progressive disclosure via reference files.

Suggestions

Add an explicit validate→fix→retry checkpoint to the update flow (e.g., 'after --update-snapshots, run npx playwright test without the flag and only commit baselines when the re-run passes') to lift workflow_clarity.

Move the full toHaveScreenshot options table and the CI workflow into separate reference files (e.g., references/options.md, references/ci.yml) and link to them from the body to improve progressive_disclosure.

Add a short verification step after baseline updates confirming the committed platform suffix matches the CI runner platform, since platform mismatch is flagged as a key failure mode.

DimensionReasoningScore

Conciseness

Lean throughout: assumes Claude's competence, skips basic explanations of what Playwright or visual regression is, and every section (options table, config, CI yaml) earns its place without padding.

3 / 3

Actionability

Provides fully executable TypeScript test snippets, a complete options table with concrete values, a copy-paste `playwright.config.ts`, exact CLI commands, and a ready-to-use GitHub Actions workflow.

3 / 3

Workflow Clarity

The first-run/update flow and CI-matching options are sequenced and the `--update-snapshots` review-the-diff warning is a checkpoint, but there is no explicit validate→fix→retry loop for the destructive baseline-rewrite operation, capping clarity at 2 per the rubric.

2 / 3

Progressive Disclosure

Well-organized into clear sections, but it is a single monolithic file with the full options reference and CI config inline; there are no one-level-deep reference files to offload detail, though external Playwright docs links are provided.

2 / 3

Total

10

/

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 highly specific, third-person, and answers both what the skill does and when to use it with an explicit trigger clause. It carves a clear niche (self-hosted Playwright visual regression) that is unlikely to conflict with adjacent skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: authors `expect(page).toHaveScreenshot()` assertions, configures masks/clips/threshold/maxDiffPixels, manages per-OS/per-browser snapshot directories, and runs the `--update-snapshots` update flow — all specific and verifiable.

3 / 3

Completeness

Clearly answers both 'what' (authors assertions, configures options, manages directories, runs update flow) and 'when' via an explicit 'Use when...' clause targeting self-hosted Playwright visual regression coverage.

3 / 3

Trigger Term Quality

Includes natural terms users would say — 'Playwright', 'visual regression', 'snapshots', 'toHaveScreenshot', '--update-snapshots', 'self-hosted' — giving good coverage of likely phrasings.

3 / 3

Distinctiveness Conflict Risk

Narrowly scoped to Playwright's self-hosted `toHaveScreenshot` flow and explicitly excludes external services, distinguishing it from hosted tools like Chromatic and reducing conflict risk.

3 / 3

Total

12

/

12

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