stub-creator
Stub Creator - Auto-activating skill for Test Automation. Triggers on: stub creator, stub creator Part of the Test Automation skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill stub-creatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just restating the skill name without explaining what it actually does. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance. The description would be nearly useless for Claude to distinguish this skill from others in a large skill library.
Suggestions
Add specific capabilities: describe what types of stubs are created (e.g., 'Creates mock objects, API stubs, and test doubles for unit testing'), what languages/frameworks are supported, and what outputs are generated.
Expand trigger terms with natural variations users would say: 'mock', 'test double', 'fake', 'spy', 'create mock for testing', plus language-specific terms like 'Jest mock', 'Mockito stub'.
Add an explicit 'Use when...' clause: 'Use when the user needs to create test doubles, mock dependencies, or generate stub implementations for unit or integration testing.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names 'Stub Creator' without explaining what concrete actions it performs. There are no specific capabilities listed - no mention of what stubs are created, for what purpose, or how. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and while it mentions triggers, they are just the skill name repeated. There is no 'Use when...' clause or meaningful guidance on when to select this skill. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'stub creator, stub creator' (duplicated). Missing natural variations users might say like 'mock', 'test double', 'fake object', 'create stub', or language-specific terms. | 1 / 3 |
Distinctiveness Conflict Risk | Being in 'Test Automation' category provides some context, and 'stub creator' is somewhat specific terminology. However, without details on what kind of stubs (API, database, service) or what languages/frameworks, it could overlap with other testing-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder template with no actual instructional content. It describes what a stub creator skill would do without providing any concrete guidance on how to create stubs, what patterns to use, or any executable code examples. The content fails on all dimensions by being verbose yet empty of actionable information.
Suggestions
Add concrete, executable code examples showing how to create stubs in specific frameworks (e.g., Jest mock functions, pytest monkeypatch, or unittest.mock)
Define a clear workflow: when to use stubs vs mocks, how to structure stub files, and validation steps to ensure stubs match interfaces
Replace generic capability descriptions with specific patterns like 'Stub external API calls: `jest.spyOn(api, 'fetch').mockResolvedValue({...})`'
Include at least one complete before/after example showing a test without stubs transformed into a test with proper stubbing
| 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. The skill mentions 'step-by-step guidance' but provides none. There are no sequences, validation steps, or any actual process to follow. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no links to examples, and no organization beyond generic section headers 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.