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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill spy-setup-helperOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely lacking in all key areas. It provides no explanation of what the skill actually does, relies on unexplained jargon ('spy setup'), and offers no guidance on when Claude should select it. The description appears to be auto-generated boilerplate rather than a thoughtful explanation of the skill's purpose.
Suggestions
Explain what 'spy setup' means in the context of test automation - describe the concrete actions like 'Creates mock objects, configures method stubs, sets up test doubles for unit testing'
Add a 'Use when...' clause with natural trigger terms users would say, such as 'mocking', 'test doubles', 'stub methods', 'unit test setup', or specific testing frameworks
Remove the redundant trigger term repetition and replace with varied, natural language terms that describe when this skill should activate
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Spy Setup Helper' without explaining what concrete actions it performs. No specific capabilities are listed - we don't know what a 'spy' is in this context or what 'setup' entails. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming itself, and provides no 'when should Claude use it' guidance. The 'Triggers on' section just repeats the skill name rather than describing use cases. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'spy setup helper' repeated twice, which is technical jargon that users are unlikely to naturally say. Missing common variations or natural language terms users might use. | 1 / 3 |
Distinctiveness Conflict Risk | While 'spy setup helper' is a specific term that wouldn't broadly conflict with many skills, the lack of explanation means it's unclear what domain this actually covers, potentially causing confusion with other test automation skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is a placeholder template with no actual content. It contains only generic boilerplate text that could apply to any skill, with no specific guidance on spy setup, no code examples, no concrete steps, and no actionable information. The skill fails to teach Claude anything about spy setup in testing frameworks.
Suggestions
Add concrete, executable code examples showing how to set up spies in Jest and/or pytest (e.g., `jest.spyOn(object, 'method')` with complete usage)
Include specific patterns for common spy scenarios: tracking calls, mocking return values, verifying call arguments
Provide a clear workflow for when to use spies vs mocks vs stubs with decision criteria
Remove all generic boilerplate ('provides automated assistance', 'follows industry best practices') and replace with actual technical content
| 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 meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does abstractly ('provides step-by-step guidance') but never actually provides any guidance, examples, or executable content. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The content only describes capabilities in vague terms without any actual sequence of actions or validation checkpoints. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed materials. No references to other files, no clear organization beyond generic headings that contain no useful content. | 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.