visual-regression

Use when reviewing CI coverage, automated checks, or test strategy related to Use visual regression testing. Focus on whether the rule is continuously verified, not just documented.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/visual-regression/SKILL.md

Quality

Content

57%

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 well-organized overview with excellent progressive disclosure to a real reference file, but it spends tokens on concepts Claude already knows, lacks in-body executable guidance, and does not present an explicitly sequenced review workflow with validation checkpoints.

Suggestions

Condense or remove the opening conceptual paragraph explaining what visual regression testing is and why functional tests miss layout bugs; lead with the actionable Quick Reference instead.

Add one minimal executable snippet in the Fix section (e.g., a Playwright `toHaveScreenshot` call or `npx playwright test --update-snapshots`) instead of deferring all code to the reference.

Reframe Check → Fix → Code Review as an explicit ordered workflow with a verification checkpoint (e.g., "confirm the CI step fails when the baseline changes") so the review path and validation step are clear in the body.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and well-sectioned, but the opening paragraph explains what visual regression testing is and why functional tests miss layout bugs — concepts Claude already knows — so it could be tightened.	2 / 3
Actionability	Concrete tool references (Playwright, Chromatic) and specific review directives are present, but the body contains no executable code or commands and the Fix section is high-level, deferring all runnable detail to the reference.	2 / 3
Workflow Clarity	The Check/Fix/Explain/Code Review sections are organized, but they are parallel modes rather than a sequenced workflow, and no explicit validation checkpoint appears in the body (verification lives in the reference).	2 / 3
Progressive Disclosure	A concise overview body points via a clearly signaled one-level-deep reference to `references/rule.md` (verified to exist and hold the detailed executable examples), matching the score-3 anchor for well-split content with easy navigation.	3 / 3
	Total	9 / 12 Passed

Description

82%

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 explicitly answers both what and when with natural trigger terms and a clear niche, though the actions are somewhat abstract and the generic CI/test-strategy triggers create overlap risk with similar rule skills.

Dimension	Reasoning	Score
Specificity	Names the domain and some actions ("reviewing CI coverage, automated checks, or test strategy", "Focus on whether the rule is continuously verified"), but the actions are abstract reviewing/focusing rather than multiple concrete capabilities, matching the score-2 anchor.	2 / 3
Completeness	An explicit "Use when..." trigger is present (so completeness is not capped at 2) alongside a clear what-statement ("Focus on whether the rule is continuously verified, not just documented"), answering both what and when.	3 / 3
Trigger Term Quality	Includes natural terms a user would say — "CI coverage", "automated checks", "test strategy", and "visual regression testing" — giving good coverage of relevant trigger keywords.	3 / 3
Distinctiveness Conflict Risk	The skill is pinned to visual regression testing (a distinct niche), but the trigger clause "reviewing CI coverage, automated checks, or test strategy" is generic and would overlap with sibling testing-rule skills, matching the score-2 anchor.	2 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/visual-regression/SKILL.md
Commit: 48405aa

Reviewed: about 6 hours ago

Table of Contents

Discovery Implementation Validation

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.