api-testing-observability-api-mock
tessl i github:sickn33/antigravity-awesome-skills --skill api-testing-observability-api-mockYou 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.
Activation
22%This description uses second person voice ('You are') which violates the style guidelines, and reads more like a persona prompt than a skill description. It lacks concrete actions, explicit trigger conditions, and natural user keywords. The description would struggle to differentiate itself in a large skill library.
Suggestions
Rewrite in third person voice describing capabilities (e.g., 'Creates mock API endpoints, generates realistic response data, simulates error conditions and latency')
Add an explicit 'Use when...' clause with trigger terms like 'mock API', 'stub endpoint', 'fake server', 'API testing', 'parallel development'
List specific concrete actions such as 'define mock endpoints', 'configure response schemas', 'simulate authentication flows', 'generate sample payloads'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Uses vague language like 'realistic mock services' and 'simulate real API behavior' without listing concrete actions. No specific capabilities like 'create mock endpoints', 'generate response schemas', or 'configure latency simulation' are mentioned. | 1 / 3 |
Completeness | Describes a general 'what' (API mocking) but lacks any explicit 'when' clause or trigger guidance. No 'Use when...' statement is present, and the use cases mentioned (development, testing, demos) are too vague to serve as clear triggers. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('API mocking', 'mock services', 'development', 'testing', 'demos') but misses common variations users might say like 'stub', 'fake API', 'mock server', 'API simulation', or specific tools/formats. | 2 / 3 |
Distinctiveness Conflict Risk | The 'API mocking' focus provides some distinction, but terms like 'development' and 'testing' are generic and could overlap with many other skills. Could conflict with general API development or testing skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
42%This skill provides a reasonable high-level framework for API mocking with good progressive disclosure, but critically lacks actionable, executable guidance. The instructions describe what to do conceptually without providing any concrete code examples, specific tools, or copy-paste ready commands that would make it immediately useful.
Suggestions
Add at least one concrete, executable code example showing a basic mock server setup (e.g., using MSW, WireMock, or a simple Express mock)
Include a specific example of a mock route definition with request/response shapes
Add validation steps such as 'Verify mock responds correctly: curl http://localhost:3000/mock/endpoint'
Remove or condense the redundant 'Context' section since it repeats information from the description
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary framing ('You are an API mocking expert...') and context sections that could be trimmed. The 'Use this skill when' and 'Do not use this skill when' sections add value but the 'Context' section is redundant. | 2 / 3 |
Actionability | The instructions are vague and abstract ('Clarify the API contract', 'Define mock routes') without any concrete code, commands, or executable examples. No actual mock server setup, no code snippets, no specific tools or frameworks mentioned. | 1 / 3 |
Workflow Clarity | Steps are listed in a logical sequence (clarify -> define -> provide fixtures -> document), but there are no validation checkpoints, no feedback loops for error handling, and the steps remain at a high conceptual level without concrete verification points. | 2 / 3 |
Progressive Disclosure | Good structure with clear overview and a single well-signaled reference to 'resources/implementation-playbook.md' for detailed implementation. The skill appropriately keeps the main file as an overview and defers code samples to a separate resource. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
63%| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 10 / 16 Passed | |
Reviewed
Table of Contents
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.