snapshot-test-helper
Snapshot Test Helper - Auto-activating skill for Test Automation. Triggers on: snapshot test helper, snapshot test helper Part of the Test Automation skill category.
36
Quality
3%
Does it follow best practices?
Impact
100%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/09-test-automation/snapshot-test-helper/SKILL.mdQuality
Discovery
7%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 description is essentially a placeholder with no substantive content. It names a category ('Test Automation') and repeats the skill name as triggers, but provides zero information about what actions the skill performs or when Claude should select it. The description would be indistinguishable from any other snapshot testing skill.
Suggestions
Add specific actions the skill performs, e.g., 'Updates snapshot baselines, compares test output against stored snapshots, identifies snapshot mismatches in Jest/Vitest tests'
Include a 'Use when...' clause with natural trigger terms like 'update snapshots', 'snapshot mismatch', 'regenerate baselines', 'jest snapshot', '.snap files'
Specify the testing framework(s) supported to distinguish from other potential snapshot testing skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Snapshot Test Helper' without describing any concrete actions. There are no specific capabilities listed - no verbs describing what the skill actually does with snapshot tests. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no explicit 'when to use' guidance. The 'Triggers on' section just repeats the skill name rather than describing actual use cases. | 1 / 3 |
Trigger Term Quality | The only trigger terms are 'snapshot test helper' repeated twice, which is redundant and unlikely to match natural user language. Missing common variations like 'snapshot testing', 'update snapshots', 'jest snapshots', or 'compare snapshots'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'snapshot test' is somewhat specific to a testing domain, the lack of detail about what kind of snapshot testing (Jest, Playwright, visual regression, etc.) means it could conflict with other testing-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a placeholder template with no actual content about snapshot testing. It contains only generic boilerplate describing what a skill should do without providing any actionable guidance, code examples, or specific information about snapshot tests in Jest, pytest, or any framework.
Suggestions
Add concrete code examples showing how to create, update, and debug snapshot tests (e.g., Jest's `toMatchSnapshot()` or pytest-snapshot usage)
Include a clear workflow for when snapshots fail: how to review diffs, update snapshots intentionally, and avoid accidental updates
Remove all generic boilerplate ('provides step-by-step guidance', 'follows industry best practices') and replace with actual snapshot testing patterns
Add specific guidance for common snapshot testing scenarios: component snapshots, inline snapshots, serializer configuration, and CI/CD considerations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about snapshot testing. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does abstractly ('provides step-by-step guidance') but never actually provides any guidance, examples, or executable content. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The content only describes trigger phrases and vague capabilities without any actual procedure for snapshot testing. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, no examples, and no organization of content by complexity or use case. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
60433a6
- 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.