BD OpenAPI Mock Server
Instant mock HTTP server from any OpenAPI 3.x or Swagger 2.0 spec. Point it at a spec file (local or URL) and get a live local server returning spec-compliant example responses — no backend code required. Wraps Stoplight Prism CLI with smart defaults. Validates the spec before starting, prints all available endpoints with example curl commands, supports validation mode (rejects non-spec requests), dynamic example selection, and auth bypass for local dev. Perfect for frontend teams blocked on a backend, contract-first API development, and integration testing without a live service. Zero external API — uses only npx and your local spec file. Triggers on "mock API", "mock server", "openapi mock", "swagger mock", "fake backend", "stub server", "contract-first", "/openapi-mock".
As a process D 42/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 42/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (OpenAPI Mock Server) differs from the folder (phy-openapi-mock-server)
- 60Tools and files. Uses tools (bash, web, python, node) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 85Steps. 12 steps, 1 vague phrases
- 100Execution cost. Instruction body is 3336 tokens
- low 13 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- +2Single-language instructions
- +5Description quotes 8 example trigger phrases
- +3Description length 784: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 12 items
- +4Has examples (16 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.