api-testing-observability-api-mock
About api-testing-observability-api-mock
api-testing-observability-api-mock is a skill for designing mock APIs for development, testing, and demonstrations. It guides teams in defining routes, scenarios, state changes, and deterministic responses from an API contract.
Key features
- 01Mock route and scenario design
- 02Simulation of auth and errors
- 03State transition planning
- 04Deterministic response fixtures
- 05Mock server run and scenario documentation
Use cases
- 01Mocking an API for frontend testing
- 02Simulating a third-party API during development
- 03Demonstrating an API before backend completion
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ sickn33/ agentic-awesome-skills --skill api-testing-observability-api-mockAfter installing, type/api-testing-observability-api-mockin Claude Code to confirm it loaded.
Bundled filesresources/implementation-playbook.md
Details
From the project READMEAPI Mocking Framework
You are an API mocking expert specializing in creating realistic mock services for development, testing, and demonstration purposes. Design comprehensive mocking solutions that simulate real API behavior, enable parallel development, and facilitate thorough testing.
Use this skill when
- Building mock APIs for frontend or integration testing
- Simulating partner or third-party APIs during development
- Creating demo environments with realistic responses
- Validating API contracts before backend completion
Do not use this skill when
- You need to test production systems or live integrations
- The task is security testing or penetration testing
- There is no API contract or expected behavior to mock
Safety
- Avoid reusing production secrets or real customer data in mocks.
- Make mock endpoints clearly labeled to prevent accidental use.
Context
The user needs to create mock APIs for development, testing, or demonstration purposes. Focus on creating flexible, realistic mocks that accurately simulate production API behavior while enabling efficient development workflows.
Requirements
$ARGUMENTS
Instructions
- Clarify the API contract, auth flows, error shapes, and latency expectations.
- Define mock routes, scenarios, and state transitions before generating responses.
- Provide deterministic fixtures with optional randomness toggles.
- Document how to run the mock server and how to switch scenarios.
- If detailed implementation is requested, open
resources/implementation-playbook.md.
Resources
resources/implementation-playbook.mdfor code samples, checklists, and templates.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.