CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ui-visual-regression

Review, triage, and validate visual regression diffs. Use when the user wants snapshot-change analysis, layout regression evidence, Storybook diffs, Playwright screenshots, or Argos review.

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./Skills/frontend-ui/ui-visual-regression/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is well-sectioned and has a clear workflow spine with validation checkpoints, but it is process philosophy rather than a working skill: no concrete commands, tool usage, or regression-classification criteria anywhere. The single external reference path does not match the actual bundle files.

Suggestions

Add concrete, executable guidance: the actual commands for producing and reviewing diffs (e.g., Playwright visual-test runs or Argos CLI review) and explicit criteria for classifying a diff as expected change vs. regression.

Fix progressive disclosure: replace or supplement the unresolvable "Infrastructure/references/deferred-skill-context/..." path with links to the real bundle files (references/contract.yaml, references/evals.yaml, references/task-profile.json).

Trim conciseness losses: remove the opening paragraph that duplicates the frontmatter description verbatim, and cut the generic Philosophy/Avoid/Anti-Patterns platitudes in favor of domain-specific gotchas.

DimensionReasoningScore

Conciseness

The body is mostly terse and list-based, but the opening paragraph duplicates the frontmatter description verbatim, and the "Philosophy", "Avoid", and "Anti-Patterns" sections are generic process platitudes ("Prefer the smallest reversible step", "evidence-first") that add no domain knowledge. This is more than the minor over-explanation of a 4, but the overall format stays lean enough to avoid a 2.

3 / 5

Actionability

The guidance is high-level throughout — "Inspect 2-3 focused surfaces", "Classify the requested mode and collect only the missing critical inputs" — with no concrete commands, tool invocations, or criteria for distinguishing regressions from expected changes. It provides high-level hints while missing the specific steps to execute, matching the anchor-2 example.

2 / 5

Workflow Clarity

A five-step numbered sequence is present with explicit checkpoints: "Stop at the first failed gate or blocker and report exact evidence" and "Rerun the relevant validation after fixes before claiming completion", plus a dedicated Validation section with a fail-fast loop. It falls short of a 5 because the steps and gates are abstract rather than concrete (no defined gates or error-recovery specifics).

4 / 5

Progressive Disclosure

Sections are well organized and the body is short, but the sole external pointer — "Infrastructure/references/deferred-skill-context/frontend-ui-ui-visual-regression/" — does not resolve to any file in the actual bundle, and the existing reference files (references/contract.yaml, references/evals.yaml, references/task-profile.json) are never mentioned. References are present but broken/unclear against the real bundle structure.

3 / 5

Total

12

/

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: it pairs a concrete what-statement with an explicit, tool-named when-clause in third person, mirroring the reference good examples. Trigger coverage is solid with only minor synonym gaps.

DimensionReasoningScore

Specificity

"Review, triage, and validate visual regression diffs" names three concrete actions on a specific domain, with minor gaps (e.g., no mention of classifying expected vs. broken changes or producing fix plans). It lists several specific actions like the anchor-4 example, but lacks the comprehensive multi-action coverage of a 5.

4 / 5

Completeness

The description explicitly answers both what ("Review, triage, and validate visual regression diffs") and when ("Use when the user wants snapshot-change analysis, layout regression evidence, Storybook diffs, Playwright screenshots, or Argos review") with concrete trigger phrases. This matches the anchor-5 structure exactly; the when-clause is fully explicit rather than merely present.

5 / 5

Trigger Term Quality

Natural trigger phrases are present — "snapshot-change analysis", "Storybook diffs", "Playwright screenshots", "Argos review" — covering the main tools users would name. A few natural synonyms are missing (e.g., "screenshot diffs", "pixel diff", "CSS regression"), which keeps it below the comprehensive synonym-level coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (visual regression diff triage) with distinct tool-specific triggers (Storybook, Playwright, Argos) that no generic review or testing skill would claim. Conflict risk with other skills is minimal.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Skills/frontend-ui/ui-visual-regression/SKILL.md

Reviewed

Table of Contents

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.