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

59%

Does it follow best practices?

Impact

86%

1.19x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/api-testing-observability-api-mock/SKILL.md

The canonical home for this skill is api-testing-observability-api-mock in rmyndharis/antigravity-skills

Quality

Content

57%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 a well-organized, concise instruction-only skill with sensible scope and safety guidance, but its guidance is high-level (no executable specifics) and it points to a playbook file that is missing. Adding validation steps and the actual referenced file would most improve it.

Suggestions

Create resources/implementation-playbook.md (or fix the path) so the twice-referenced playbook actually exists; a broken reference undermines navigation.

Add a concrete runnable example in the body (e.g. a minimal mock server command or a route/scenario snippet) to lift actionability past high-level direction.

Add a validation/checklist step in the Instructions (e.g. verify the mock matches the contract, confirm scenarios switch correctly) to introduce a feedback loop into the workflow.

Dimension	Reasoning	Score
Conciseness	The body is lean with tight, useful sections (Use when / Do not use when / Safety / Instructions); the main trim opportunity is the 'Context' section, which restates the opening paragraph and is mild padding, but it is not heavily verbose so it stays efficient.	4 / 5
Actionability	Instructions are specific concepts ('Define mock routes, scenarios, and state transitions', 'deterministic fixtures with optional randomness toggles') but high-level with no code, commands, or tool names, and the executable detail is deferred to a reference file, so key execution details are missing.	3 / 5
Workflow Clarity	A rough sequence exists (clarify contract -> define routes/scenarios/state -> provide fixtures -> document running/switching), but there are no validation checkpoints or feedback loops, matching the 'sequence present but checkpoints missing' anchor.	3 / 5
Progressive Disclosure	Section structure is clean and the playbook reference is clearly signaled one level deep, but the referenced file resources/implementation-playbook.md does not exist (no resources/ directory present), so the promised navigation is broken rather than merely a minor gap.	3 / 5
	Total	13 / 20 Passed

Description

61%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 clearly states what the skill does and carves out a distinct API-mocking niche, with solid natural trigger terms. Its main weakness is the missing explicit 'when to use' guidance, which caps completeness.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks to mock, stub, or fake an API for frontend, integration, or demo work.'

Add concrete actions and synonyms — 'stub endpoints', 'fake API server', 'simulate latency/auth/errors' — to lift specificity and trigger coverage.

Mention file/protocol cues users naturally say (e.g. 'mock REST/GraphQL endpoints', '.openapi/.swagger specs') to sharpen distinctiveness.

Dimension	Reasoning	Score
Specificity	It names the domain ('API mocking expert', 'realistic mock services') and a couple of concrete actions ('Design mocks that simulate real API behavior', 'enable parallel development'), but these are abstract rather than the multiple specific concrete actions (stub endpoints, define latency, state transitions) that anchor 4/5 require.	3 / 5
Completeness	The 'what' is clear ('Design mocks that simulate real API behavior and enable parallel development') but there is no explicit 'Use when...' clause in the description, and the rubric caps completeness at 3 when trigger guidance is absent.	3 / 5
Trigger Term Quality	It surfaces natural terms a user would say — 'API mocking', 'mock services', 'development, testing, and demos' — giving good keyword coverage, though common synonyms like 'stub' or 'fake API/server' are missing, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	'API mocking' is a clear, fairly specific niche with distinct triggers and only minor overlap risk with general testing or testing-framework skills; it is not as tightly scoped as anchor 5 but is well above the broad anchor 3.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/api-testing-observability-api-mock/SKILL.md
Commit: 900c504

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