Index of every page on this site: llms.txt
All skills
Run it yourself

Generate mock API servers for testing and development with realistic response data. Use when creating mock APIs for development and testing. Trigger with phrases like "create mock API", "generate API mock", or "setup mock server".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/mocking-apis

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈61 tokens for metadata: the name and description. ≈1.1k when used: this file. ≈2k more on demand in 3 files.

Description uses 3.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈245 characters, or 3.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Mocking APIs

Overview

Generate mock API servers from OpenAPI specifications that return realistic, schema-compliant response data for development and testing. Support dynamic response generation with Faker.js data, configurable latency simulation, stateful CRUD behavior, and request recording for contract testing validation.

Prerequisites

  • OpenAPI 3.0+ specification file with response schema definitions
  • Mock server runtime: Prism (Stoplight), json-server, MSW (Mock Service Worker), or WireMock
  • Faker.js or equivalent for realistic test data generation
  • Docker for containerized mock server deployment (optional but recommended)
  • Frontend or consumer application needing API stubs for parallel development

Instructions

  1. Read the OpenAPI specification using Read and extract all endpoint definitions, response schemas, and example values to build the mock response inventory.
  2. Generate response fixtures for each endpoint using schema-aware data generation: realistic names (Faker), valid emails, properly formatted dates, and relational IDs that reference other mock entities.
  3. Configure the mock server to match requests by method, path pattern, query parameters, and request body content type, returning the appropriate fixture.
  4. Add stateful behavior for CRUD operations: POST creates a record in memory, GET returns it, PUT updates it, DELETE removes it -- enabling realistic integration testing flows.
  5. Implement configurable response delays (50-500ms per endpoint) to simulate real-world latency and test client timeout handling.
  6. Add error scenario mocking: configure specific request patterns to return 400, 401, 404, 429, or 500 responses for testing error handling paths.
  7. Enable request recording that captures all incoming requests with timestamps and headers for later replay in contract tests.
  8. Create a startup script that launches the mock server on a configurable port with hot-reload when fixture files change.

See references/implementation.md for the full implementation guide.

Output

  • ${CLAUDE_SKILL_DIR}/mocks/server.js - Mock server entry point with route registration
  • ${CLAUDE_SKILL_DIR}/mocks/fixtures/ - Per-endpoint response fixture JSON files
  • ${CLAUDE_SKILL_DIR}/mocks/generators/ - Dynamic response generators using Faker.js
  • ${CLAUDE_SKILL_DIR}/mocks/scenarios/ - Error scenario configurations (4xx, 5xx responses)
  • ${CLAUDE_SKILL_DIR}/mocks/state.js - In-memory state store for CRUD behavior
  • ${CLAUDE_SKILL_DIR}/mocks/recordings/ - Captured request logs for contract testing
  • ${CLAUDE_SKILL_DIR}/docker-compose.mock.yml - Docker configuration for mock server

Error Handling

Error Cause Solution
Schema mismatch Mock response does not match updated OpenAPI spec Run spec-to-fixture sync on spec change; add CI check comparing fixture schemas
Missing endpoint Consumer requests path not defined in OpenAPI spec Return 501 with message listing available endpoints; log unknown path for spec update
Stale fixtures Mock data becomes unrealistic after API schema evolution Regenerate fixtures from latest spec; use generators over static fixtures for evolving APIs
Port conflict Mock server port already in use by another dev service Make port configurable via environment variable; default to spec-defined server URL port
State leak between tests Stateful mock retains data from previous test run Reset in-memory state before each test suite; expose POST /mock/reset admin endpoint

Refer to references/errors.md for comprehensive error patterns.

Examples

Frontend parallel development: Launch a Prism mock server from the OpenAPI spec so frontend developers can build against realistic API responses while backend implementation is in progress.

Integration test isolation: Use MSW (Mock Service Worker) to intercept HTTP requests in Node.js test suites, returning fixture responses without network calls, with per-test response customization.

Contract testing: Record all requests to the mock server during frontend E2E tests, then replay them against the real backend to verify the mock accurately represents actual API behavior.

See references/examples.md for additional examples.

Resources

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts27d3 checks · Risk SAFE
  • Gen Agent Trust Hub27d

    This skill allows for the creation of mock API servers using well-known tools like Prism and MSW. It is safe for development use, though it carries a standard risk associated with processing external OpenAPI specification files.

  • Socket27d

    No alerts

  • Snyk27d

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated last month
What it can do
Reads files Edits files Runs commands
version
1.25.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
[
  "api",
  "testing",
  "mocking-apis"
]
All 6 allowed tools
ReadWriteEditGrepGlobBash(api:mock-*)
Other metadata
compatibility
Designed for Claude Code

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/mocking-apis