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.
36
Quality
3%
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 severely underdeveloped, consisting only of a skill name, a redundant trigger phrase, and a broad category label. It provides no information about what the skill actually does, what specific capabilities it offers, or when Claude should select it over other testing-related skills.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Creates spy functions for intercepting method calls, configures return values, and tracks call arguments in test suites').
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when setting up test spies, mocking functions, creating stubs, or working with jest.spyOn, sinon spies, or test doubles').
Specify the testing frameworks or contexts this applies to (e.g., Jest, Sinon, Vitest) to distinguish it from other test automation skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions - 'Spy Setup Helper' is a name, not a capability description. There's no indication of what the skill actually does (e.g., creates spies, configures mocks, generates test doubles). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming a category ('Test Automation'). There is no 'Use when...' clause or explicit trigger guidance - only a redundant trigger phrase. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'spy setup helper' repeated twice, which is the skill name itself. Missing natural terms users would say like 'mock', 'stub', 'test double', 'jest spy', 'sinon', etc. | 1 / 3 |
Distinctiveness Conflict Risk | 'Test Automation' is extremely broad and would conflict with any testing-related skill. Nothing distinguishes this from other test automation skills like mock generators, assertion helpers, or test runners. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a generic template with no actual content about spy setup. It contains only boilerplate descriptions of what a skill should do without any concrete guidance on setting up spies in Jest, pytest, or any testing framework. The content fails to teach Claude anything actionable about the topic.
Suggestions
Add executable code examples showing spy setup in specific frameworks (e.g., Jest's jest.spyOn(), pytest's mocker.spy())
Replace generic capability descriptions with concrete patterns like 'spy on method calls', 'verify call arguments', 'restore original implementation'
Include a quick-start section with copy-paste ready spy setup code for the most common use case
Add validation steps such as 'verify spy was called with expected arguments' with actual assertion examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about spy setup. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific examples are provided. The content describes what the skill does abstractly but never shows how to actually set up a spy in any testing framework. | 1 / 3 |
Workflow Clarity | No steps, sequences, or processes are defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or actual workflow instructions. | 1 / 3 |
Progressive Disclosure | The content has some structure with clear section headers, but there are no references to detailed materials. For a skill about spy setup, there should be links to framework-specific guides or examples. | 2 / 3 |
Total | 5 / 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
60433a6
- 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.