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 is an extremely weak skill description that essentially only provides a name and category with no substantive content. It fails on all dimensions: no concrete actions are listed, trigger terms are just the skill name duplicated, there is no 'when to use' guidance, and it lacks the specificity needed to distinguish it from other testing skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates and configures spy/mock/stub objects for unit tests, sets up return values, and verifies call expectations.'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user needs to set up test spies, mocks, stubs, test doubles, or configure jest.spyOn/sinon spies for unit testing.'
Remove the duplicated trigger term and instead list varied natural keywords users would say, such as 'mock setup', 'test spy', 'stub configuration', 'test double', specific framework names like 'jest', 'sinon', 'vitest'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. 'Spy Setup Helper' is a name, not a description of capabilities. There is no indication of what specific actions this skill performs (e.g., creating mock objects, configuring spies, setting up test doubles). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the vague title, and the 'when' clause is essentially just the skill name repeated. There is no explicit trigger guidance or use-case description. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('spy setup helper, spy setup helper'). There are no natural user keywords like 'mock', 'stub', 'test double', 'jest.spyOn', 'sinon', or other terms a user would naturally use when needing this functionality. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too vague to be distinctive. 'Test Automation' is a broad category, and without specific capabilities described, this could conflict with any testing-related skill. The term 'spy setup' is somewhat niche but insufficiently elaborated. | 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 with no actual instructional content. It repeatedly references 'spy setup helper' without ever explaining what a spy is in testing, how to set one up, or providing any code examples for Jest, pytest, or any other framework. The entire content could be replaced by a single sentence and would convey the same (zero) information.
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 generic 'Capabilities' and 'Purpose' boilerplate with actual step-by-step instructions for common spy setup patterns (e.g., spying on methods, asserting call arguments, restoring originals).
Include a workflow with validation steps, such as: 1) identify the function to spy on, 2) set up the spy with specific return values, 3) run the test, 4) assert spy was called correctly, 5) clean up/restore.
Remove all meta-description content ('This skill provides automated assistance...') and replace with actionable technical content that Claude doesn't already know, such as framework-specific gotchas or patterns.
| 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 provides zero actual technical content about spy setup in testing frameworks. | 1 / 3 |
Actionability | There are no concrete code examples, commands, or executable guidance. The content only describes what the skill could do in abstract terms ('provides step-by-step guidance', 'generates production-ready code') without actually doing any of it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. There are no instructions for how to actually set up spies in Jest, pytest, or any framework. The skill contains no sequenced actions or validation checkpoints. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative page with no meaningful structure. There are no references to detailed materials, no code examples to organize, and the sections present (Purpose, When to Use, Capabilities) contain only generic placeholder text. | 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.