mocking-apis

Generate mock API servers for testing and development with realistic response data. Use when creating mock APIs for development and testing. Trigger with phrases like "create mock API", "generate API mock", or "setup mock server".

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/api-development/api-mock-server/skills/mocking-apis/SKILL.md

Quality

Content

57%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized skill body that uses progressive disclosure effectively, pointing to real reference files for detail. The main gaps are the absence of inline executable code and a missing validation checkpoint in the workflow.

Suggestions

Add a small inline executable example (e.g., a one-line Prism or json-server launch command) so the body is immediately actionable without opening a reference.

Insert an explicit validation step in the Instructions (e.g., curl the mock after startup and assert a 200/schema-compliant response) to close the workflow-verification gap.

Tighten the Output section by merging it into the Instructions or trimming file listings that are implied by the steps.

Dimension	Reasoning	Score
Conciseness	The body is reasonably lean and avoids explaining concepts Claude already knows, but the Instructions are descriptive prose and the Output/Resources sections add tokens that could be tightened.	2 / 3
Actionability	It gives concrete specifics (latency 50-500ms, status codes 400/401/404/429/500, POST /mock/reset) but provides no inline executable code in the body, deferring all code to the referenced files.	2 / 3
Workflow Clarity	The eight numbered steps are clearly sequenced, but there is no validation or verification checkpoint to confirm the mock server behaves correctly before use.	2 / 3
Progressive Disclosure	The body is a clear overview with well-signaled, one-level-deep references to real files (implementation.md, errors.md, examples.md) and cleanly organized sections.	3 / 3
	Total	9 / 12 Passed

Description

90%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-structured description with an explicit 'Use when' trigger and natural trigger phrases, written in correct third-person voice. Its only weakness is that it names a single core action rather than enumerating several concrete capabilities.

Suggestions

Enumerate a few more concrete capabilities in the opening sentence (e.g., schema-aware fixtures, stateful CRUD, latency and error simulation) to raise specificity to the top level.

Dimension	Reasoning	Score
Specificity	The description states one concrete action ('Generate mock API servers... with realistic response data') and names the domain, but does not list multiple specific concrete actions like the score-3 anchor does.	2 / 3
Completeness	It explicitly answers both 'what' (generate mock API servers with realistic response data) and 'when' via an explicit 'Use when creating mock APIs...' trigger clause.	3 / 3
Trigger Term Quality	It provides natural phrases a user would actually say ('create mock API', 'generate API mock', 'setup mock server'), giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The mock-API-server niche is clear and the triggers are distinct, making it unlikely to fire for the wrong skill.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/api-development/api-mock-server/skills/mocking-apis/SKILL.md
Commit: 0540a62

Reviewed: about 12 hours ago

Table of Contents

Discovery Implementation Validation

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.