CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/storybook-visual-regression-testing

Sets up visual regression coverage for a Storybook project - either via the official @chromatic-com/storybook addon (hosted) or via @storybook/test-runner with a postVisit hook that calls Playwright's toHaveScreenshot (self-hosted). Covers test-runner install, lifecycle hooks (setup / preVisit / postVisit), and CI integration. Use when a repo already has a working `.storybook/` config and the team wants per-story visual coverage rather than page-level snapshots.

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.

A well-structured, actionable skill body covering both visual-regression paths with executable code and a complete CI workflow; its only weakness is minor explanatory prose that could be trimmed.

Suggestions

Tighten the 'How it works' line and the Chromatic UI activation walkthrough to assume Claude's familiarity, removing explanatory filler.

The lifecycle hooks table has a formatting error (missing closing backtick on the postVisit row) that should be fixed for clean rendering.

DimensionReasoningScore

Conciseness

Mostly lean and assumes familiarity with Storybook/Playwright, but prose like 'turns every story into an executable test powered by Jest + Playwright under the hood' and the Chromatic UI walkthrough ('Sign into Chromatic... click Catch a UI change') could be tightened.

2 / 3

Actionability

Provides copy-paste-ready, executable artifacts: npm install commands, package.json snippet, a complete test-runner.ts config, two-step run commands, and a full CI workflow yaml.

3 / 3

Workflow Clarity

Sequences the two-step run process and CI pipeline with explicit gotchas (wait-on before test-storybook, concurrently -k to kill the server), and guards artifact upload with if: always().

3 / 3

Progressive Disclosure

Well-organized into clearly labeled sections with one-level-deep references to external docs and companion skills; no nested reference chains, and the body appropriately delegates toHaveScreenshot and Chromatic CLI details outward rather than inlining them.

3 / 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.

A strong, third-person description that names both hosted and self-hosted paths, lists concrete capabilities, and gives an explicit Use-when trigger with clear scoping against sibling skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across two paths: 'install', 'lifecycle hooks (setup / preVisit / postVisit)', 'CI integration', and 'calls Playwright's toHaveScreenshot', matching the multiple-specific-actions anchor.

3 / 3

Completeness

States what it does ('Sets up visual regression coverage...') and an explicit when clause ('Use when a repo already has a working `.storybook/` config and the team wants per-story visual coverage rather than page-level snapshots'), satisfying both halves.

3 / 3

Trigger Term Quality

Covers natural terms a user would say — 'visual regression coverage', 'Storybook', 'per-story visual coverage', 'page-level snapshots' — with the domain vocabulary the target audience actually uses.

3 / 3

Distinctiveness Conflict Risk

Niche is clearly scoped to Storybook visual regression and explicitly defers overlapping concerns to companion skills ('chromatic-visual-regression-testing', 'playwright-snapshots'), minimizing conflict.

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