api-mock-generator
Api Mock Generator - Auto-activating skill for API Development. Triggers on: api mock generator, api mock generator Part of the API Development skill category.
36
3%
Does it follow best practices?
Impact
100%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/15-api-development/api-mock-generator/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 essentially a placeholder that provides almost no useful information for skill selection. It repeats the skill name as triggers, lacks any concrete capability descriptions, and provides no guidance on when Claude should select this skill over others. The description would be indistinguishable from dozens of other potential API-related skills.
Suggestions
Add specific capabilities: 'Generates mock API endpoints with configurable responses, creates stub servers for testing, simulates REST/GraphQL APIs with realistic data'
Include a proper 'Use when...' clause: 'Use when the user needs to test against an API that doesn't exist yet, wants to simulate API responses, or mentions mock server, fake API, or API testing'
Add natural trigger term variations: 'mock server', 'fake API', 'stub endpoints', 'API simulation', 'test doubles', 'API testing'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Api Mock Generator' and 'API Development' without describing any concrete actions. There are no specific capabilities listed like 'generates mock endpoints', 'creates stub responses', or 'simulates API behavior'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' guidance is just a duplicate of the skill name rather than explicit trigger scenarios or use cases. | 1 / 3 |
Trigger Term Quality | The triggers listed are redundant ('api mock generator, api mock generator') and miss natural variations users would say like 'mock API', 'fake endpoint', 'stub server', 'test API', or 'API simulation'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'API mock' is somewhat specific to a niche, the lack of detail about what distinguishes this from other API-related skills (testing, documentation, client generation) creates potential overlap with the broader 'API Development' category mentioned. | 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 content is essentially a placeholder template with no actual instructional value. It describes what the skill claims to do but provides zero actionable guidance on API mock generation - no code examples, no tool recommendations, no workflows, and no concrete steps. Claude already knows what API mocking is; this skill adds nothing useful.
Suggestions
Add executable code examples showing how to create API mocks using specific tools (e.g., MSW, Prism, json-server, or WireMock)
Include a concrete workflow: 1) Define OpenAPI spec, 2) Generate mock server, 3) Validate responses, 4) Integrate with tests
Provide specific input/output examples showing a sample API endpoint and its corresponding mock configuration
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about API mock generation. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that waste tokens without adding value. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does in abstract terms but never shows how to actually generate an API mock - no examples, no libraries, no executable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The content only describes trigger conditions and vague capabilities without any process guidance. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative document with no references to detailed materials, no links to examples or API references, and no structured navigation to deeper content. | 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
b8a3b3e
- 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.