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.
34
0%
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
0%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 fails on all dimensions: it names no concrete actions, includes no natural trigger terms beyond its own repeated name, provides no 'when to use' guidance, and is indistinguishable from any other testing skill. It needs a complete rewrite.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates, updates, and compares snapshot test files for UI components and serialized output.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user mentions snapshot tests, updating snapshots, .snap files, Jest snapshots, baseline comparisons, or visual regression testing.'
Remove the duplicate trigger term ('snapshot test helper' is listed twice) and replace with varied, natural keywords users would actually say when needing this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. It only names itself ('Snapshot Test Helper') and its category ('Test Automation') without describing what it actually does—no verbs like 'generates', 'compares', 'updates', etc. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no explanation of capabilities and no explicit 'Use when...' clause with trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'snapshot test helper' repeated twice, which is the skill's own name rather than natural keywords a user would say. Missing terms like 'snapshot testing', 'update snapshots', 'jest snapshots', '.snap files', 'baseline comparison', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it could overlap with any testing-related skill. Without specifying what kind of snapshot tests, which frameworks, or what actions it performs, there is high conflict risk with other test automation skills. | 1 / 3 |
Total | 4 / 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 is a hollow template/placeholder skill with no actual instructional content. It repeatedly references 'snapshot test helper' without ever explaining what snapshot testing is, how to implement it, or providing any executable code or concrete guidance. The entire body is meta-description about what the skill could do rather than actually doing it.
Suggestions
Add concrete, executable code examples for snapshot testing (e.g., Jest's `toMatchSnapshot()` or pytest snapshot plugins) with actual test file content.
Include a clear workflow for creating, updating, and reviewing snapshot tests, with validation steps like 'run `jest --updateSnapshot` only after reviewing diff'.
Remove all meta-description sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actionable content: quick start code, common patterns, and troubleshooting for snapshot mismatches.
Add specific guidance on snapshot test best practices such as when to use inline vs file snapshots, how to handle large snapshots, and how to avoid brittle tests.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section restates the same vague idea ('snapshot test helper') without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code examples, no commands, no specific steps for creating or managing snapshot tests. The content describes rather than instructs, offering only vague promises like 'provides step-by-step guidance' without actually delivering any. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill merely states it can provide guidance without showing any process. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of placeholder text with no references to detailed files, no structured navigation, and no meaningful content organization. Section headers exist but contain no substantive content to organize. | 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
c8a915c
- 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.