stub-creator
Stub Creator - Auto-activating skill for Test Automation. Triggers on: stub creator, stub creator Part of the Test Automation skill category.
33
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 extremely minimal and template-like, providing almost no useful information for skill selection. It lacks concrete actions, meaningful trigger terms, and any 'Use when...' guidance. The duplicated trigger term and boilerplate structure suggest this was auto-generated without meaningful customization.
Suggestions
Add specific concrete actions describing what the skill does, e.g., 'Generates stub functions, mock objects, and test doubles for unit testing frameworks such as Jest, pytest, or JUnit.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create stubs, mocks, fakes, test doubles, or needs to stub out dependencies for unit tests.'
Remove the duplicated trigger term and expand with natural variations users would say, such as 'mock', 'test double', 'fake implementation', 'stub out', 'create test stubs'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Stub Creator' and mentions 'Test Automation' but provides no concrete actions. There is no explanation of what creating a stub entails—no mention of generating mock objects, creating test doubles, producing stub files, or any specific operations. | 1 / 3 |
Completeness | The 'what' is extremely vague (just 'Stub Creator') and the 'when' is missing entirely—there is no 'Use when...' clause or equivalent explicit trigger guidance. The description fails to answer either question adequately. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'stub creator, stub creator' (duplicated). It misses natural variations users might say like 'mock', 'test double', 'fake', 'stub out', 'create stubs', 'test stubs', or language-specific terms. The terms are repetitive and narrow. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'stub creator' is somewhat specific to a niche (test stubs), which provides some distinctiveness. However, the vague 'Test Automation' category label could overlap with other testing-related skills, and without concrete actions it's unclear how this differs from mock generators or other test helper 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 shell with no substantive content. It consists entirely of generic boilerplate that describes what a skill would do without actually teaching anything about stub creation. There is no actionable guidance, no code examples, no workflow, and no references to useful resources.
Suggestions
Add concrete, executable code examples showing how to create stubs in at least one framework (e.g., Jest's jest.fn(), pytest's unittest.mock) with specific input/output patterns.
Define a clear workflow for when and how to create stubs: identify dependencies → create stub → configure return values → inject into test → verify behavior.
Remove all generic boilerplate sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actual technical content about stub patterns, anti-patterns, and best practices.
Add references to framework-specific detailed guides (e.g., JEST_STUBS.md, PYTEST_MOCKS.md) if the topic warrants more depth than a single file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'stub creator' excessively, and provides zero substantive information about how to actually create stubs. | 1 / 3 |
Actionability | There are no concrete code examples, commands, or executable guidance. The content only describes what the skill supposedly does in vague terms ('provides step-by-step guidance') without actually providing any guidance. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for creating stubs, no validation checkpoints, and no sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative page with no references to detailed materials, no links to examples or related files, and no meaningful structure beyond generic boilerplate headings. | 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
3076d78
- 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.