spy-setup-helper
Spy Setup Helper - Auto-activating skill for Test Automation. Triggers on: spy setup helper, spy setup helper Part of the Test Automation skill category.
34
0%
Does it follow best practices?
Impact
99%
0.99xAverage 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/spy-setup-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 critically weak across all dimensions. It reads like an auto-generated stub with no meaningful content—just a name repeated as a trigger term and a broad category label. It provides no information about what the skill actually does, when it should be used, or how it differs from other testing skills.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Generates spy/mock/stub setup code for test frameworks like Jest, Sinon, or Jasmine. Configures function spies, return values, and call tracking.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about setting up spies, mocks, stubs, test doubles, or needs help with jest.spyOn, sinon.spy, or similar test instrumentation.'
Remove the duplicate trigger term ('spy setup helper' listed twice) and replace with varied natural language terms users would actually use, such as 'mock function', 'spy on method', 'stub API call', 'test double setup'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. 'Spy Setup Helper' is a name, not a description of capabilities. There are no specific actions like 'creates spy objects', 'configures mock functions', or 'sets up test doubles'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the vague title, and the 'when' clause is just a self-referential trigger ('spy setup helper'). There is no explicit guidance on when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'spy setup helper' repeated twice, which is not a natural phrase users would say. Missing natural terms like 'mock', 'stub', 'jest.spyOn', 'sinon', 'test double', 'fake function', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The phrase 'Test Automation' is extremely broad and could conflict with many testing-related skills. Without specifying what kind of spies, which frameworks, or what specific problem it solves, it's indistinguishable from 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 skill is an empty template/placeholder with no actual instructional content. It repeatedly references 'spy setup helper' without ever explaining what a spy is, how to set one up, or providing any code examples for Jest, pytest, or any other framework mentioned in the tags. The entire body could be replaced with a single sentence: 'This skill exists' — it adds no value to Claude's capabilities.
Suggestions
Add concrete, executable code examples showing how to set up spies in at least one framework (e.g., Jest's jest.spyOn() or Python's unittest.mock), with specific input/output demonstrations.
Replace the vague 'Capabilities' section with an actual step-by-step workflow for common spy setup patterns, including validation steps (e.g., verifying spy was called with expected arguments).
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Purpose') that describe the skill meta-information rather than teaching how to do the task — these waste tokens without adding actionable content.
Add framework-specific sections or references (e.g., jest-spies.md, pytest-mocking.md) with copy-paste-ready patterns for spy creation, assertion, and cleanup.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'spy setup helper' excessively, and contains zero substantive information about how to actually set up spies in any testing framework. | 1 / 3 |
Actionability | There are no concrete code examples, no executable commands, no specific library usage, and no actual instructions. Every section is vague and abstract — 'Provides step-by-step guidance' without providing any actual steps. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, 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 placeholder text with no references to supporting files, no structured navigation, and no meaningful organization of content. There are no bundle files to reference either, but the body itself lacks any real 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
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.