stub-creator
Stub Creator - Auto-activating skill for Test Automation. Triggers on: stub creator, stub creator Part of the Test Automation skill category.
33
Quality
3%
Does it follow best practices?
Impact
85%
1.02xAverage 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/stub-creator/SKILL.mdQuality
Discovery
7%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, providing almost no useful information for skill selection. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance. The redundant trigger term and generic 'Test Automation' category label do not compensate for the missing substantive content.
Suggestions
Add specific concrete actions describing what the skill creates (e.g., 'Creates mock objects, API stubs, and test doubles for unit testing').
Include a 'Use when...' clause with natural trigger terms like 'mock', 'fake', 'test double', 'stub out', 'mock service', 'unit test setup'.
Specify the context or file types this applies to (e.g., 'for JavaScript/TypeScript projects', 'when writing Jest tests') to improve distinctiveness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'Stub Creator' without explaining what stubs are created, how they're created, or what concrete actions the skill performs. 'Auto-activating skill for Test Automation' is abstract and provides no specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the vague 'Stub Creator' label, and the 'when' guidance is limited to the redundant trigger phrase. There is no explicit 'Use when...' clause or meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'stub creator, stub creator' (duplicated). This misses natural variations users might say like 'create mock', 'test double', 'fake object', 'mock service', or 'generate stubs'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'stub creator' is somewhat specific to test automation, the lack of detail about what kind of stubs (API stubs, function stubs, service stubs) could cause overlap with other testing or code generation skills. | 2 / 3 |
Total | 5 / 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 placeholder that provides no actual guidance on creating stubs. It consists entirely of meta-descriptions about what the skill supposedly does without any concrete instructions, code examples, or actionable content. The skill would need to be completely rewritten with actual stub creation patterns, code examples, and specific guidance.
Suggestions
Add concrete, executable code examples showing how to create stubs in specific frameworks (e.g., Jest mock functions, pytest fixtures, or unittest.mock)
Define what a 'stub' is in this context and provide specific patterns: function stubs, API stubs, database stubs with actual implementation code
Include a clear workflow: 1) Identify dependency to stub, 2) Create stub with specific syntax, 3) Inject stub into test, 4) Verify stub behavior
Remove all meta-descriptions ('This skill provides...', 'Capabilities include...') and replace with direct instructions and examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The entire skill describes what it does rather than instructing how to create stubs. There are no executable examples or copy-paste ready content. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. The skill claims to provide 'step-by-step guidance' but contains zero actual steps. There's no sequence, no validation, and no process to follow. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of marketing-style text with no structure for discovery. No references to detailed materials, no links to examples or advanced content, and no clear organization beyond generic headers. | 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
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.