json-api-mock-generator_skill

This skill generates realistic JSON API mock responses with nested structures, proper types, and configurable record counts for fast development.
  • TypeScript

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill ehtbanton/claudeskillsrepo --skill json-api-mock-generator

  • SKILL.md4.1 KB

Overview

This skill generates production-realistic JSON API mock response files for development, testing, and prototyping. It creates valid .json outputs named using the mock-{resource}-{endpoint}.json convention and produces realistic data types, nested structures, and configurable record counts. The generator defaults to sensible RESTful wrappers and 10 records for list endpoints when minimal context is provided.

How this skill works

When invoked with a trigger phrase (for example: "create mock API response", "generate JSON mock data", "fake API data for", or "mock endpoint response"), the skill immediately emits a complete JSON file with no clarifying questions unless the domain is ambiguous. It builds list, single-resource, or error responses following standard wrapper patterns, populates fields with realistic fake values (UUIDs, ISO-8601 timestamps, emails, names, amounts), and ensures consistent IDs and types across relationships.

When to use it

  • Create realistic list responses for frontend development and pagination testing
  • Generate single-resource payloads for component integration or API contract tests
  • Produce error response samples (404, 422, 500) for error handling and UI states
  • Seed automated tests with deterministic but realistic mock records
  • Prototype new endpoints quickly without backend implementation

Best practices

  • Specify resource name, endpoint, and record count when possible to get precise output
  • Use UUIDs for primary keys unless you explicitly need sequential integers
  • Include domain hints (e-commerce, user, SaaS) to receive domain-specific fields
  • Validate the generated JSON against your API schema and the provided checklist before use
  • Keep mock files under version control and update them when the API contract changes

Example use cases

  • mock-posts-list.json — 10 realistic blog posts with authors, tags, content snippets, and view counts
  • mock-users-list.json — 25 users with nested address objects, avatars, roles, and created_at timestamps
  • mock-product-list.json — e-commerce product catalog with SKUs, price in cents, inventory, and image objects
  • mock-error-404.json — standardized error payload with code, message, details array, and ISO timestamp
  • mock-subscription-single.json — SaaS subscription resource with plan object, period dates, and status

FAQ

Lists default to 10 records unless you request a different count.

Are IDs UUIDs by default?

Yes — primary keys use UUIDs by default. Sequential integers are used only when explicitly requested.

Does the generator validate JSON before output?

Yes — it ensures valid JSON, consistent data types, unique IDs within the file, valid ISO-8601 timestamps, and no trailing commas.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
json-api-mock-generator skill by ehtbanton/claudeskillsrepo | VeilStrat