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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill snapshot-test-helperOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, functioning more as a placeholder than a useful skill description. It provides no information about what the skill actually does, what actions it can perform, or when Claude should select it. The only distinguishing element is the 'snapshot test' terminology, but this alone is insufficient for effective skill selection.
Suggestions
Add specific capabilities describing what the skill does, e.g., 'Creates, updates, and debugs snapshot tests. Compares actual output against stored snapshots, identifies mismatches, and helps update baseline snapshots.'
Add a 'Use when...' clause with natural trigger terms like 'snapshot testing', 'update snapshots', 'snapshot mismatch', 'jest snapshots', '.snap files', 'baseline comparison'
Remove the redundant duplicate trigger term and replace with varied, natural phrases users would actually say when needing snapshot test assistance
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Snapshot Test Helper') and category ('Test Automation') without describing any concrete actions. There are no verbs indicating what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no capabilities listed) and 'when should Claude use it' (no explicit use-case guidance beyond the redundant trigger phrase). Both components are missing. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'snapshot test helper' repeated twice, which is the skill name itself rather than natural keywords users would say. Missing terms like 'snapshot testing', 'update snapshots', 'jest snapshots', '.snap files', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'snapshot test' is somewhat specific to a testing domain, which provides some distinctiveness. However, without concrete actions or clear triggers, it could still overlap with general testing skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no actual content. It consists entirely of generic placeholder text that describes what a skill should do without providing any concrete guidance on snapshot testing. There is no actionable information, no code examples, and no real instructions.
Suggestions
Add concrete, executable code examples for snapshot testing (e.g., Jest's `expect(component).toMatchSnapshot()` or pytest snapshot patterns)
Include specific workflow steps: how to create snapshots, update them when intentional changes occur, and review snapshot diffs
Provide actual guidance on snapshot test best practices such as when to use snapshots vs explicit assertions, handling dynamic content, and organizing snapshot files
Remove all generic boilerplate text and replace with lean, specific instructions that assume Claude's competence
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are meaningless filler without actual content. | 1 / 3 |
Actionability | There is zero concrete guidance, no code examples, no commands, and no actual instructions for snapshot testing. The entire content describes what the skill supposedly does rather than providing any executable guidance. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no structure pointing to detailed materials. There are no references to other files, no organized sections with actual content, and no navigation aids. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.