api-mock-generator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill api-mock-generatorApi Mock Generator - Auto-activating skill for API Development. Triggers on: api mock generator, api mock generator Part of the API Development skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder that relies entirely on the skill name without providing meaningful detail. It lacks concrete actions, natural trigger terms, and explicit usage guidance. The redundant trigger terms and boilerplate structure suggest auto-generated content that needs substantial human refinement.
Suggestions
Add specific capabilities: 'Generates mock API responses, creates stub endpoints, simulates REST/GraphQL APIs for testing'
Include a proper 'Use when...' clause: 'Use when the user needs to test against an API that doesn't exist yet, create fake endpoints, or simulate API responses for development'
Expand trigger terms with natural variations: 'mock API, fake endpoint, stub server, API simulation, test doubles, mock responses, .json fixtures'
| 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 responses', 'creates stub endpoints', or 'simulates API behavior'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no explicit 'when to use' guidance. The 'Triggers on' section is not a proper 'Use when...' clause with meaningful context. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('api mock generator' listed twice) and overly specific. Missing natural variations users would say like 'mock API', 'fake endpoint', 'stub server', 'test API', or 'simulate responses'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'API mock generator' is a somewhat specific domain, the lack of detail about what distinguishes this from other API-related skills (testing, documentation, client generation) creates potential overlap risk. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no substantive guidance on API mock generation. It lacks any executable code, concrete examples, specific tools (like MSW, Prism, or json-server), or actionable workflows. The content tells Claude what the skill is supposed to do without ever showing how to do it.
Suggestions
Add concrete, executable code examples showing how to generate API mocks using specific tools (e.g., MSW for JavaScript, Prism for OpenAPI specs, or WireMock for Java)
Include a clear workflow: 1) Parse API spec/define endpoints, 2) Generate mock responses, 3) Validate mock behavior, 4) Integrate with test suite
Remove generic boilerplate sections ('When to Use', 'Example Triggers') and replace with actual implementation guidance
Add example input (e.g., an OpenAPI snippet) and expected output (e.g., generated mock server code) to make the skill actionable
| 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 code snippets, no tool references. | 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 for accomplishing the task. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative document with no references to detailed materials, no links to examples or advanced features, and no structured navigation to additional resources. | 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.