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 to describe any concrete capabilities, lacks natural trigger terms users would use, and provides no guidance on when Claude should select this skill. It would be indistinguishable from other testing-related skills in a multi-skill environment.
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 and replace with varied, natural keywords users would actually say when needing snapshot test help.
| 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', or any specific capabilities. | 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—only a category label and a redundant trigger phrase. | 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. 'Test Automation' is a broad category, and without specific actions or file types, there is nothing to distinguish this from other test-related 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 skill is an empty placeholder with no actionable content. It consists entirely of generic boilerplate that describes what the skill would do without actually doing it. There are no code examples, no concrete instructions, no workflow steps, and no references to supporting materials.
Suggestions
Add concrete, executable code examples for snapshot testing (e.g., Jest's `toMatchSnapshot()`, pytest snapshot plugins) with actual test cases showing creation, updating, and reviewing snapshots.
Define a clear workflow: 1) Write component/function, 2) Create snapshot test, 3) Run and generate snapshot, 4) Review snapshot file, 5) Update snapshots when intentional changes occur — with validation steps for each.
Remove all boilerplate sections (Purpose, When to Use, Example Triggers, Capabilities) and replace with actionable content such as common snapshot patterns, pitfalls (e.g., non-deterministic data), and commands for updating/clearing snapshots.
Add specific guidance for handling snapshot failures, including how to diff snapshots, when to update vs. investigate, and how to avoid brittle snapshots (e.g., serializer configuration, ignoring dynamic fields).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the trigger phrase numerous times, and contains zero substantive information about snapshot testing. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code examples, no commands, no specific steps for creating, updating, or debugging snapshot tests. Every section is vague and abstract. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The skill merely claims it 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to supporting files, no structured navigation, and no bundle files to support it. There is nothing to progressively disclose. | 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
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.