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.
72
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is a strong skill description that clearly communicates what it does (generates snapshot test files for React components), when to use it (with explicit trigger phrases), and how it accepts input. It uses third person voice, is concise, and has excellent trigger term coverage with minimal conflict risk.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description specifies a concrete action: generating snapshot test files for Sentry frontend React components. It also mentions accepting an optional component path or name via $ARGUMENTS, adding further specificity. | 3 / 3 |
Completeness | Clearly answers both 'what' (generate snapshot test files for Sentry frontend React components) and 'when' (explicit 'Use when' clause with multiple trigger phrases). Also documents the $ARGUMENTS parameter. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger phrases: 'generate snapshot tests', 'add snapshot tests', 'create visual snapshots', 'write snapshot tests', 'add visual regression tests', 'snapshot this component'. These are phrases users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — scoped specifically to snapshot tests for Sentry frontend React components. The trigger terms are narrowly focused on snapshot/visual regression testing, making it unlikely to conflict with general testing or other component-related skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality, highly actionable skill with clear workflow steps, executable code examples, and useful decision tables. Its main weakness is length — the full examples section and some explanatory text add bulk that could be trimmed or split into a separate reference file. The anti-patterns section and final checklist are strong additions that help prevent common mistakes.
Suggestions
Move the three full examples (Button, Switch, Alert) into a separate EXAMPLES.md and reference it from the main skill to reduce token cost while preserving the detailed guidance.
Remove explanatory sentences that describe what code examples already demonstrate (e.g., 'The third argument to it.snapshot.each is the metadata function — include all props that vary in the snapshot') since Claude can infer this from the code.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is thorough and mostly efficient, but it's quite long (~250 lines) with some redundancy. The full examples at the end (Button, Switch, Alert) repeat the same boilerplate patterns already shown in Step 4, and some explanatory text like 'The third argument to it.snapshot.each is the metadata function' explains things Claude can infer from the code examples. | 2 / 3 |
Actionability | Excellent actionability — every step includes fully executable, copy-paste-ready TypeScript/TSX code. Import paths, ESLint suppression comments, container sizing, prop classification, and anti-patterns are all concrete and specific. The decision tables for import paths and prop types are immediately usable. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced from locating the component through writing the file, with explicit ordering guidance for snapshot cases. The checklist at the end serves as a validation checkpoint. The prop classification table provides clear decision criteria for each step. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and tables, but it's monolithic — all content is in a single file with no references to supporting files. The three full examples (Button, Switch, Alert) could be split into a separate EXAMPLES.md to reduce the main file's length while keeping the core instructions lean. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- getsentry/sentry
- Commit
552fb5c
- 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.