managing-snapshot-tests
This skill enables Claude to manage and update snapshot tests using intelligent diff analysis and selective updates. It is triggered when the user asks to analyze snapshot failures, update snapshots, or manage snapshot tests in general. It helps distinguish intentional changes from regressions, selectively update snapshots, and validate snapshot integrity. Use this when the user mentions "snapshot tests", "update snapshots", "snapshot failures", or requests to run "/snapshot-manager" or "/sm". It supports Jest, Vitest, Playwright, and Storybook frameworks.
89
53%
Does it follow best practices?
Impact
96%
1.00xAverage score across 9 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./backups/skills-migration-20251108-070147/plugins/testing/snapshot-test-manager/skills/snapshot-test-manager/SKILL.mdQuality
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 well-crafted skill description that clearly articulates specific capabilities, provides explicit trigger guidance with natural user terms, and occupies a distinct niche. It uses proper third-person voice throughout and balances detail with conciseness. The inclusion of both natural language triggers and command shortcuts further strengthens its completeness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'analyze snapshot failures', 'update snapshots', 'distinguish intentional changes from regressions', 'selectively update snapshots', 'validate snapshot integrity'. Also names specific frameworks (Jest, Vitest, Playwright, Storybook). | 3 / 3 |
Completeness | Clearly answers both 'what' (manage/update snapshot tests via diff analysis, distinguish regressions, selective updates, validate integrity) and 'when' with an explicit 'Use this when...' clause listing specific trigger phrases and commands. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'snapshot tests', 'update snapshots', 'snapshot failures', plus command triggers '/snapshot-manager' and '/sm'. Also mentions specific framework names users would reference. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused specifically on snapshot testing management. The specific trigger terms ('snapshot tests', 'snapshot failures', '/snapshot-manager', '/sm') and named frameworks make it very unlikely to conflict with other skills like general testing or code review skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content reads like a marketing description rather than actionable instructions for Claude. It lacks any concrete commands, code examples, or specific tool usage for any of the four frameworks it claims to support (Jest, Vitest, Playwright, Storybook). The content describes what the skill does in abstract terms without ever telling Claude how to actually do it.
Suggestions
Add concrete, executable commands for each supported framework (e.g., `npx jest --updateSnapshot --testPathPattern=<file>`, `npx vitest --update`, `npx playwright test --update-snapshots`)
Replace the abstract example narratives with actual workflow steps showing how to read snapshot diff output, identify intentional vs. unintentional changes, and selectively update specific snapshots
Add validation checkpoints such as re-running tests after updates to confirm only intended snapshots changed, and a feedback loop for handling remaining failures
Remove the 'Overview', 'When to Use This Skill', 'Best Practices', and 'Integration' sections which add no actionable value, and replace them with framework-specific concrete instructions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and padded with unnecessary context. Sections like 'Overview', 'How It Works', 'When to Use This Skill', and 'Integration' largely restate information Claude already knows or that belongs in frontmatter metadata. The 'Best Practices' section states obvious advice like 'Clear Communication' and 'Avoid blindly updating all snapshots.' | 1 / 3 |
Actionability | There are no concrete commands, executable code, or specific tool invocations. The examples describe what 'the skill will' do in abstract terms ('Analyze the snapshot failures, highlighting the unexpected diffs') without providing any actual commands, code snippets, or specific steps Claude should execute. No framework-specific commands (e.g., `jest --updateSnapshot`, `npx playwright test --update-snapshots`) are provided. | 1 / 3 |
Workflow Clarity | The multi-step processes described are vague and lack concrete sequencing. Steps like 'Analyze the snapshot failures' and 'Update the relevant snapshot files' provide no specific instructions on how to perform these actions. There are no validation checkpoints, no error recovery steps, and no feedback loops for what is inherently a process involving destructive changes to snapshot files. | 1 / 3 |
Progressive Disclosure | The content is organized into logical sections with headers, which provides some structure. However, there are no references to external files, no bundle files to support deeper content, and the content that exists is mostly filler rather than substantive material that would benefit from being split across files. | 2 / 3 |
Total | 5 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Commit
13d35b8
- 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.