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.

1.19x

Quality

28%

Does it follow best practices?

Impact

86%

1.19x

Average score across 3 eval scenarios

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.

This description reads as a persona prompt ('You are an expert') rather than a functional skill description, using second-person framing and vague language. It lacks concrete actions, explicit trigger guidance, and natural user keywords. The API mocking domain provides some distinctiveness, but the description fails to clearly communicate what specific tasks the skill performs or when it should be selected.

Suggestions

Replace the persona framing ('You are an API mocking expert') with third-person action verbs listing concrete capabilities, e.g., 'Generates mock API endpoints, creates response fixtures, simulates error codes and latency, and produces OpenAPI-compatible stubs.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to mock an API, create test stubs, fake endpoints, simulate API responses, or set up a mock server for parallel development.'

Remove vague buzzwords like 'enable parallel development' and 'realistic mock services' and replace with specific deliverables or file types (e.g., 'WireMock configs, MSW handlers, JSON response 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 'what' is vaguely described (design mocks) and there is no explicit 'when' clause or trigger guidance. The description reads more like a persona statement ('You are an expert') than a skill description, and lacks a 'Use when...' clause, which should cap completeness at 2 at best—but the weak 'what' brings it to 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 or testing skills, but the vague framing ('development, testing, and demos') could overlap with broader testing or API development skills.	2 / 3
	Total	6 / 12 Passed

Implementation

35%

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

This skill reads more like a role description than actionable guidance. It lacks any concrete code examples, specific commands, or executable patterns for API mocking, instead relying entirely on abstract directives and deferring all implementation detail to a referenced resource file. The structure is reasonable but the content fails to provide the immediate, actionable value expected of a skill file.

Suggestions

Add at least one concrete, executable code example showing a basic mock server setup (e.g., using msw, json-server, or Express) so the skill is immediately actionable without needing the referenced playbook.

Replace abstract instructions like 'Clarify the API contract' with specific steps including example inputs/outputs, such as a sample OpenAPI snippet and the corresponding mock route definition.

Add a validation checkpoint in the workflow, e.g., 'Verify mock responses match the API contract schema before proceeding to integration testing.'

Remove the opening paragraph that restates the role description—Claude already has this context from the skill metadata.

Dimension	Reasoning	Score
Conciseness	The skill includes some unnecessary framing ('You are an API mocking expert...') and context that Claude already knows. The 'Use this skill when' and 'Do not use this skill when' sections add moderate value but are somewhat verbose. The core instructions are reasonably lean.	2 / 3
Actionability	The skill provides no concrete code, commands, or executable examples. Instructions like 'Clarify the API contract' and 'Define mock routes' are abstract directives without specific implementation guidance. There are no code snippets, no example mock definitions, and no copy-paste ready content.	1 / 3
Workflow Clarity	The instructions section provides a rough sequence of steps (clarify contract → define routes → provide fixtures → document), but lacks explicit validation checkpoints, error recovery steps, or feedback loops. The workflow is implicit rather than clearly sequenced.	2 / 3
Progressive Disclosure	There is a reference to `resources/implementation-playbook.md` for detailed implementation, which is good progressive disclosure. However, the main content itself lacks a quick-start example or concrete overview content that would make the skill immediately useful without needing to open the referenced file.	2 / 3
	Total	7 / 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: 636b862

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