mocking-apis

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill 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".

51%

Overall

Validation — 81%

Implementation — 7%

Activation — 90%

SKILL.md

Review

Evals

Validation

81%

Warnings & errors only

Criteria	Description	Result
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

	Total	13 / 16 Passed

Implementation

This skill content is largely a template with placeholder text that provides no actionable guidance for creating mock API servers. It lacks any concrete code examples, specific mock server frameworks (like MSW, json-server, or Prism), or executable commands. The content describes generic API development rather than the specific task of mocking APIs for testing.

Suggestions

Add concrete, executable code examples for at least one mock server framework (e.g., json-server setup, MSW handlers, or Prism configuration)

Remove redundant overview text and generic prerequisites that don't add value specific to mock API generation

Consolidate the two separate numbered instruction lists into a single clear workflow with validation steps (e.g., 'verify mock server responds correctly')

Include specific example mock data generation patterns and realistic response structures rather than just referencing external files

Dimension	Reasoning	Score
Conciseness	Contains significant padding and redundancy - the overview repeats itself ('This skill provides automated assistance' appears twice), includes generic prerequisites Claude already knows (like 'Development environment with necessary frameworks installed'), and lists obvious concepts without adding value.	1 / 3
Actionability	Provides only vague, abstract guidance with no concrete code examples, specific commands, or executable snippets. Instructions like 'Generate boilerplate code using Bash(api:mock-*)' and 'Implement endpoint handlers with business logic' describe rather than instruct.	1 / 3
Workflow Clarity	Steps are poorly organized with duplicate numbered lists (two separate '1-5' sequences), no clear sequencing between phases, and no validation checkpoints. For mock API generation which could involve file creation, there's no verification step.	1 / 3
Progressive Disclosure	References external files (implementation.md, errors.md, examples.md) which is appropriate structure, but the main content is poorly organized and the references feel like placeholders rather than well-signaled navigation to specific content.	2 / 3
	Total	5 / 12 Passed

Activation

90%

This is a solid description with excellent trigger term coverage and completeness. The explicit 'Use when' and 'Trigger with phrases' clauses make it highly actionable for skill selection. The main weakness is that the capability description could be more specific about what concrete actions the skill performs beyond generating mock servers.

Suggestions

Expand the capability description to list specific actions like 'configure endpoints, define response schemas, simulate error conditions, generate realistic test data'

Dimension	Reasoning	Score
Specificity	Names the domain (mock API servers) and mentions 'realistic response data' but doesn't list multiple specific concrete actions like endpoint configuration, response customization, or specific data types supported.	2 / 3
Completeness	Clearly answers both what (generate mock API servers with realistic response data) and when (explicit 'Use when' clause plus 'Trigger with phrases' providing concrete examples).	3 / 3
Trigger Term Quality	Explicitly lists natural trigger phrases users would say: 'create mock API', 'generate API mock', 'setup mock server'. Also includes relevant keywords like 'testing', 'development', and 'mock APIs'.	3 / 3
Distinctiveness Conflict Risk	Clear niche focused specifically on mock API servers for testing/development. The specific trigger phrases like 'mock API', 'mock server' are distinct and unlikely to conflict with general API or testing skills.	3 / 3
	Total	11 / 12 Passed

Reviewed

17 days ago

Table of Contents

Validation Implementation Activation

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.