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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill managing-snapshot-tests89
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 96%
↑ 1.00xAgent success when using this skill
Validation for skill structure
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 an excellent skill description that hits all the marks. It provides specific capabilities, comprehensive trigger terms that users would naturally use, explicit 'Use when' guidance, and a clearly defined niche in snapshot test management. The inclusion of supported frameworks adds helpful context without being verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'manage and update snapshot tests', 'intelligent diff analysis', 'selective updates', 'distinguish intentional changes from regressions', 'validate snapshot integrity'. Also specifies supported frameworks (Jest, Vitest, Playwright, Storybook). | 3 / 3 |
Completeness | Clearly answers both what (manage snapshot tests, diff analysis, selective updates, validate integrity) AND when with explicit 'Use this when...' clause listing specific trigger phrases and commands. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'snapshot tests', 'update snapshots', 'snapshot failures', '/snapshot-manager', '/sm'. These are exactly what developers would type when needing this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on snapshot testing. The combination of 'snapshot' terminology, specific frameworks, and dedicated commands (/snapshot-manager, /sm) makes it highly unlikely to conflict with other testing or file management 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 is almost entirely descriptive rather than instructive. It explains what snapshot management is and describes hypothetical workflows without providing any concrete commands, code examples, or executable guidance. Claude already understands snapshot testing concepts; this skill should instead provide specific commands for each framework (Jest, Vitest, Playwright, Storybook) and clear decision criteria for distinguishing intentional changes from regressions.
Suggestions
Add concrete, executable commands for each supported framework (e.g., 'jest --updateSnapshot', 'vitest -u', 'playwright test --update-snapshots')
Replace abstract examples with actual code showing how to analyze a snapshot diff and the specific criteria for determining if a change is intentional vs a regression
Remove the 'Overview', 'How It Works', and 'When to Use' sections - these explain concepts Claude already knows. Start directly with actionable guidance
Add a workflow with explicit validation steps: run tests -> analyze specific failures -> confirm with user -> update selectively -> re-run to verify
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains concepts Claude already knows (what snapshot tests are, how they work). Phrases like 'This skill empowers Claude' and 'streamlined approach' are filler. The entire document describes rather than instructs. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance provided. The examples describe what 'the skill will' do abstractly but provide no actual commands, code snippets, or specific steps Claude should execute. | 1 / 3 |
Workflow Clarity | Steps are vague descriptions ('Analyze the snapshot failures', 'Update the relevant snapshot files') with no actual commands, validation checkpoints, or error recovery. No specific framework commands (e.g., 'jest -u', 'vitest --update') are provided. | 1 / 3 |
Progressive Disclosure | The content has some structure with clear sections (Overview, How It Works, Examples, Best Practices), but everything is inline with no references to external files. The content that exists could be much more concise. | 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.
- 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.