mockstar-mock

name	mockstar-mock
description	Generate a runnable mockstar mock server for a service from its specs and docs. Use when asked to mock a service, stand up a fake/stub API, create mockstar mocks/fixtures, or scaffold a mock backend from an API spec or documentation. Accepts OpenAPI (json/yaml), Postman collections, HAR captures, curl examples, GraphQL SDL/introspection, and prose docs (Markdown/PDF/DOCX or a documentation URL); normalizes every input into one Endpoint Inventory, uses native `mockstar import` for OpenAPI and hand-authors the rest, infers scenarios/dynamic handlers/webhooks at full fidelity, runs `mockstar enhance` for Tier 2 placeholders, then boots the server and smoke-tests every route. Tags each mock with provenance and confidence and emits a coverage report flagging speculative inferences and documented-but-unmocked gaps. Not for the mockstar HTTPS proxy or native GraphQL semantics. Targets the mockstar CLI (`bunx @dhaneshpurohit/mockstar`).
x-spec-version	1
license	MIT
compatibility	Requires Bun (`bunx @dhaneshpurohit/mockstar` >= 0.2.2) or Docker (ghcr.io/dhanesh/mockstar), plus `uv` and `curl` for the bundled helpers.
metadata	{"author":"dhanesh","version":"1.0.1","tags":"mockstar,mock-server,openapi,postman,har,graphql,api-testing"}

mockstar-mock

Converts any combination of API specs and docs into a runnable mockstar mock project. It accepts OpenAPI 3.x (JSON/YAML), Postman collections, HAR captures, curl command files, GraphQL SDL/introspection, and prose documentation (Markdown, PDF, DOCX, or a URL) — one or several at once — and produces a fully configured mockstar project with realistic scenarios, dynamic handlers, and webhooks, verified by booting the server and smoke-testing every route.

The defining rule: no fabricated endpoints. Every mock traces back to a fetched or provided source. Behavior that is reasoned from context rather than explicitly documented is tagged confidence: "inferred" in the Endpoint Inventory and flagged in the coverage report. Speculation is visible and reviewable; it is never silently promoted to ground truth.

When to use

Use when you need to stand up a mock backend quickly from existing specs or documentation: mocking a third-party API for local development, building a test double from an OpenAPI spec, scaffolding fixtures from a HAR capture of real traffic, or generating stubs from API prose docs. Works on any mix of input types; the skill normalizes them all into one Endpoint Inventory before generating.

When not to use

• mockstar HTTPS proxy mode — this skill generates config-driven mocks; it does not configure the mockstar proxy for intercepting live traffic.
• Native GraphQL server semantics — GraphQL is modeled as a single POST /graphql endpoint with operation routing via scenarios[].when.body. If you need a proper GraphQL resolver server (subscriptions, schema stitching, persisted queries), use a dedicated GraphQL toolchain.
• Non-mockstar mock servers — MSW, Prism, WireMock, json-server. This skill targets only the mockstar CLI.

Prerequisites

• bunx @dhaneshpurohit/mockstar available (install: bun add -g @dhaneshpurohit/mockstar or use bunx directly with Bun). Package name matters: mockstar is published on npm as the scoped package @dhaneshpurohit/mockstar (latest ≥ 0.2.2). The unscoped mockstar on npm is an unrelated project — never invoke bare bunx mockstar. Equivalent Docker image: ghcr.io/dhanesh/mockstar:latest (--runtime docker). The importer's schema-derived bodies and mixed-segment path-param handling require mockstar ≥ 0.2.2; the coverage report records the resolved runtime and version.
• uv available — used to run for binary input conversion.