CtrlK
BlogDocsLog inGet started
Tessl Logo

generate-snapshot-tests

Generate snapshot test files for Sentry frontend React components. Use when asked to "generate snapshot tests", "add snapshot tests", "create visual snapshots", "write snapshot tests", "add visual regression tests", or "snapshot this component". Accepts an optional component path or name via $ARGUMENTS.

70

Quality

86%

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

SKILL.md
Quality
Evals
Security

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.

A highly actionable, well-structured workflow skill with copy-paste-ready examples and clear sequencing. The main opportunities are adding an explicit run-tests validation step and potentially externalizing the worked examples to reduce inline bulk.

Suggestions

Add an explicit final step instructing Claude to run the generated snapshot tests (e.g. the relevant jest command) and report failures, closing the workflow validation gap.

Consider moving the three full worked examples (Button, Switch, Alert) into a separate references file (e.g. examples.md) and summarizing them inline, to improve progressive disclosure for a 340-line skill.

Reduce repeated import/theme boilerplate across examples by referencing the canonical 'Required imports' block once, trimming minor conciseness overhead.

DimensionReasoningScore

Conciseness

The body is almost entirely actionable code and decision tables and assumes Claude's knowledge of React/TypeScript/Jest, with only minor repetition of import boilerplate across the three worked examples that could be tightened.

4 / 5

Actionability

Fully executable, copy-paste-ready code with three complete worked examples (Button, Switch, Alert) covering common cases, plus concrete decision tables for import paths, prop classification, and container sizing.

5 / 5

Workflow Clarity

A clear five-step sequence is paired with a final verification checklist, but there is no explicit feedback loop such as running the generated snapshot tests to confirm they pass, leaving a minor validation gap.

4 / 5

Progressive Disclosure

No bundle files are present and the skill is a single self-contained file with clear, well-labeled sections; the three full inlined examples could be externalized into reference files, a minor organization gap for a ~340-line document.

4 / 5

Total

17

/

20

Passed

Description

90%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, well-scoped description with explicit what/when structure, comprehensive natural trigger phrases, and a clearly distinct niche. The only minor gap is that it names a single concrete action rather than enumerating several.

DimensionReasoningScore

Specificity

Names the domain ('Sentry frontend React components') and one concrete action ('Generate snapshot test files') but does not enumerate multiple distinct actions, matching the anchor for 1-2 concrete actions rather than comprehensive coverage.

3 / 5

Completeness

Explicitly answers both 'what' (generate snapshot test files for Sentry React components) and 'when' (Use when asked to ... with concrete trigger phrases), and notes $ARGUMENTS handling.

5 / 5

Trigger Term Quality

Six natural user phrases are listed including synonyms ('snapshot tests', 'visual snapshots', 'visual regression tests', 'snapshot this component'), providing comprehensive coverage of terms a user would actually say.

5 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Sentry React component snapshot tests) with distinct, specific triggers and minimal overlap risk with other skills.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
getsentry/sentry
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.