CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/percy-visual-regression-testing

Authors Percy visual snapshot tests via the @percy/cli + framework SDK (Playwright, Cypress, Selenium, Storybook), runs them with `percy exec -- {test command}`, configures viewports / masking / ignored regions, and reviews diffs in the Percy build UI. Use when the project ships visual regression coverage to BrowserStack Percy.

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 highly actionable, well-structured skill body with executable code, a clear workflow, and an explicit review/approval feedback loop. The only weakness is mild verbosity — a redundant references list and some prose that could be trimmed.

Suggestions

Remove or prune the bottom 'References' section, which restates links already defined and used inline; rely on the inline link definitions for navigation.

Tighten the Overview and config-file prose (e.g. 'the schema evolves with major versions and reproducing it from memory risks drift') to the essential fact to cut tokens.

Consider moving the per-snapshot options and `percy exec` flags tables into a bundled reference file so the SKILL.md body stays a lean overview.

DimensionReasoningScore

Conciseness

Mostly efficient and reference-dense (no basic-concept explanations), but ~200 lines with a redundant bottom References section restating links already defined inline and some prose that could be tightened.

2 / 3

Actionability

Fully executable guidance throughout — concrete `npm install` commands, a runnable Playwright JS snippet, real `percy exec --` invocations, and a complete copy-paste CI workflow YAML.

3 / 3

Workflow Clarity

Clear install→author→run→review→CI sequence with an explicit diff-approval feedback loop ('require explicit approval before the build is marked passed', PR stays 'pending' until approved) and a `--dry-run` verification option.

3 / 3

Progressive Disclosure

Well-organized into clearly headed sections with one-level-deep, clearly signaled external references (GitHub README links) and a dedicated References list; no nested bundle indirection (no bundle files exist).

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 description: third-person, concrete multi-action capabilities, and an explicit 'Use when' trigger tied to a distinctive BrowserStack Percy niche. No vague fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Authors Percy visual snapshot tests', 'runs them with `percy exec -- {test command}`', 'configures viewports / masking / ignored regions', 'reviews diffs in the Percy build UI' — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what (authors/runs/configures/reviews) and when via the explicit trigger 'Use when the project ships visual regression coverage to BrowserStack Percy.'

3 / 3

Trigger Term Quality

Covers natural terms a user would say — 'visual snapshot tests', 'visual regression coverage', 'Percy', 'BrowserStack Percy', 'diffs' — rather than only technical jargon.

3 / 3

Distinctiveness Conflict Risk

The Percy/BrowserStack visual-regression niche is sharply scoped with a distinct trigger, making conflict with other testing skills unlikely.

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