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

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/api-testing-observability-api-mock/SKILL.md

Quality

Content

61%Weight 40%Scale 1-5

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

The body is concise and reasonably well-structured with a single offloaded reference, but it lacks a sequenced workflow with validation checkpoints and the actionability remains high-level rather than executable.

Suggestions

Reorder the Instructions into a numbered, sequenced workflow with an explicit verification step (e.g., start the mock server and confirm a sample request returns the expected fixture).

Add one concrete executable example, such as a minimal route definition or a command to run the mock server.

Resolve the reference path: the body points to 'resources/implementation-playbook.md' but no bundle directory named 'resources/' is present; align the path with the actual bundle location.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-organized with no concept over-explanation; only mild filler in the Context section ('Focus on creating flexible, realistic mocks...') keeps it from a 5.	4 / 5
Actionability	Instructions are concrete directives ('Clarify the API contract...', 'Define mock routes, scenarios, and state transitions') but stay high-level with no executable specifics, commands, or fixture formats.	3 / 5
Workflow Clarity	The Instructions are a loose bulleted list rather than a sequenced workflow, and there are no validation or verification checkpoints for the mock server output.	3 / 5
Progressive Disclosure	Good section structure with a clearly signaled one-level reference to implementation-playbook.md, but the referenced path uses 'resources/' while no bundle directory by that name exists, leaving the reference unverifiable.	4 / 5
	Total	14 / 20 Passed

Description

66%Weight 40%Scale 1-5

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 is specific and well-keyworded with a clear niche, but it lacks an explicit 'Use when...' trigger clause that would make Claude confidently select it.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers, e.g. 'Use when building mock APIs, stubbing third-party services, or creating demo backends.'

Expand the action list toward comprehensive coverage (e.g., 'stub endpoints, simulate latency and errors, manage scenarios').

Include natural synonyms like 'stub', 'fake server', and 'sandbox' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the API-mocking domain and several concrete actions ('simulate real API behavior', 'enable parallel development', for 'development, testing, and demos'), but the action list is not comprehensive enough for a 5.	4 / 5
Completeness	The 'what' is clear (design realistic mock services) but there is no explicit 'Use when...' trigger clause, so per the guideline completeness is capped at 3; the 'when' is only weakly implied.	3 / 5
Trigger Term Quality	Strong natural keywords ('API mocking', 'mock services', 'development, testing, and demos') that users would actually say, though it omits common synonyms such as 'stub' or 'fake server'.	4 / 5
Distinctiveness Conflict Risk	'API mocking' is a clear, mostly distinct niche with only minor overlap risk against general testing skills.	4 / 5
	Total	15 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/api-testing-observability-api-mock/SKILL.md
Commit: 3eff4af

Reviewed: 16 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.