api-testing-observability-api-mock

You are an API mocking expert specializing in realistic mock services for development, testing, and demos. Design mocks that simulate real API behavior and enable parallel development.

Quality

21%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/antigravity-api-testing-observability-api-mock/SKILL.md

Quality

Discovery

22%

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

The description reads more like a persona statement ('You are an API mocking expert') than a functional skill description, using second-person voice which violates the third-person requirement. It lacks concrete actions, explicit trigger guidance, and natural user keywords, making it difficult for Claude to reliably select this skill from a large pool.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks to mock an API, create stubs, fake endpoints, or simulate API responses for testing.'

Replace the persona framing with specific concrete actions in third person, e.g., 'Generates mock API endpoints, creates realistic response fixtures, simulates error codes and latency, and configures mock servers for parallel development.'

Include natural trigger terms users would say, such as 'mock server', 'stub API', 'fake endpoint', 'test double', 'API simulation', 'WireMock', 'MSW', or '.json fixtures'.

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'design mocks that simulate real API behavior' and 'enable parallel development' without listing concrete actions. No specific operations (e.g., 'generate mock endpoints', 'create response fixtures', 'simulate error codes') are mentioned.	1 / 3
Completeness	The description loosely addresses 'what' (design API mocks) but has no explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is entirely missing, which per the rubric should cap completeness at 2, and the 'what' is also quite vague, bringing this to a 1.	1 / 3
Trigger Term Quality	Contains some relevant keywords like 'API mocking', 'mock services', 'development', 'testing', and 'demos', but misses common user terms like 'stub', 'fake API', 'mock server', 'test doubles', 'API simulation', or specific tool names.	2 / 3
Distinctiveness Conflict Risk	The 'API mocking' domain is somewhat specific and distinguishable from general coding skills, but the broad mention of 'development, testing, and demos' could overlap with general testing skills or API development skills.	2 / 3
	Total	6 / 12 Passed

Implementation

20%

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

This skill is essentially a high-level role description with vague instructions rather than an actionable guide. It lacks any concrete code examples, specific tool recommendations, or executable commands that would help Claude actually create mock APIs. The content explains what Claude should do conceptually but never shows how, and much of the text restates things Claude already understands.

Suggestions

Add concrete, executable code examples for at least one mock server framework (e.g., MSW, WireMock, or Express-based mocks) with copy-paste-ready configurations.

Replace vague instructions like 'Clarify the API contract' with specific steps, templates, or example mock definitions (e.g., a sample route definition with request/response pairs).

Remove the 'Use this skill when' / 'Do not use this skill when' / 'Context' sections or drastically condense them — these explain concepts Claude already knows and consume tokens without adding actionable value.

Provide the referenced `resources/implementation-playbook.md` bundle file, or inline the most critical content (checklists, templates) directly in the skill body.

Dimension	Reasoning	Score
Conciseness	The content is verbose and explains concepts Claude already knows (what API mocking is, when to use it, generic safety advice). The 'Use this skill when' and 'Do not use this skill when' sections add little actionable value. Much of the content reads like a role description rather than operational instructions.	1 / 3
Actionability	There are no concrete code examples, executable commands, or specific mock server implementations. Instructions like 'Clarify the API contract' and 'Define mock routes' are vague directives rather than actionable guidance. No specific tools, frameworks, or copy-paste-ready configurations are provided.	1 / 3
Workflow Clarity	The Instructions section provides a rough sequence of steps (clarify contract → define routes → provide fixtures → document), but there are no validation checkpoints, no feedback loops for verifying mock correctness, and no explicit verification steps before serving mocks.	2 / 3
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed content, which is a good one-level-deep reference. However, no bundle files are provided, so the reference is unverifiable. The main content itself is thin on substance, making the reference feel like a deferral rather than a well-structured split.	2 / 3
	Total	6 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: boisenoise/skills-collections
Commit: 431bfad

Reviewed: 2 days 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.