CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/chromatic-visual-regression-testing

Use when visual regression tests run on Chromatic Cloud for Storybook, Playwright or Cypress: the chromatic CLI, baselines, TurboSnap, UI Review, CI gating and reading exit codes to tell visual changes from errors.

Quality

88%

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

82%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 operationally excellent single-file skill: copy-paste-ready commands, config, CI workflow, and code, with lean tables replacing prose and a genuine error-recovery story via exit codes and debug flags. The remaining headroom is minor: slight redundancy between the description, "When to use", and "References" sections, and the flag/exit-code tables could be split out to trim the main file.

DimensionReasoningScore

Conciseness

The body is dense and operational — tables, flags, and code with almost no concept-explanation padding ("Chromatic is a visual testing platform built by the team behind Storybook" is one line of useful context, not a tutorial). Minor trims are possible: the "When to use" bullets partially restate the description, and the References section re-annotates links already cited inline.

4 / 5

Actionability

Fully executable throughout: copy-paste commands (`npm install --save-dev chromatic`, `npx chromatic --project-token <token>`), a complete flag table, a `chromatic.config.json` example, a ready-to-use GitHub Actions workflow with the `fetch-depth: 0` TurboSnap requirement, and runnable `modes.ts`/`preview.ts`/`isChromatic()` code samples covering the common cases.

5 / 5

Workflow Clarity

A clear sectioned progression (install → connect/baseline → author stories → run in CI) with a real feedback toolkit: the exit-code table encodes the gate decision (treat `1` differently from `3`/`21`–`23`/`101`–`105`), and `--dry-run`, `--list`, `--trace-changed`, `--diagnostics-file` support error recovery. It falls short of the top anchor because steps are section headers rather than an explicit validated sequence.

4 / 5

Progressive Disclosure

As a single-file skill with no bundle directories, it is well organized (Overview / When to use / Authoring / Running / TurboSnap / CI / References) with every section at the right altitude for an operational skill. The full flag and exit-code tables could arguably live in a reference file given the ~310-line length, which keeps it off the top anchor.

4 / 5

Total

17

/

20

Passed

Description

87%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 strong description with an explicit, specific trigger clause and a concrete inventory of capability areas anchored to a distinct product niche. The only shortfall is that capabilities are named as topics rather than actions, and a few natural synonyms (e.g. "visual testing", "snapshot testing") are absent.

DimensionReasoningScore

Specificity

Lists several concrete capability areas — "the chromatic CLI, baselines, TurboSnap, UI Review, CI gating and reading exit codes to tell visual changes from errors" — but these are noun-phrase topics rather than verb-driven actions, leaving minor gaps versus the comprehensive anchor.

4 / 5

Completeness

Explicitly answers both: "Use when visual regression tests run on Chromatic Cloud for Storybook, Playwright or Cypress" is a concrete, specific trigger clause, and the colon-separated list explicitly states what the skill covers (CLI, baselines, TurboSnap, UI Review, CI gating, exit-code reading).

5 / 5

Trigger Term Quality

Good natural keyword coverage: "visual regression tests", "Chromatic Cloud", "Storybook", "Playwright", "Cypress", "chromatic CLI", "TurboSnap", "CI", "exit codes" — terms users would genuinely say. A few common synonyms ("visual testing", "snapshot testing") are missing, short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

"Chromatic Cloud" plus "TurboSnap" and "the chromatic CLI" carve out a clear niche with distinct triggers; the Chromatic qualifier keeps Playwright/Cypress mentions from colliding with generic test-runner skills, so conflict risk is minimal.

5 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

On this page