api-mock-helper
Produces mock server definitions, sandbox environment specs, API stub configurations, and fixture data for any API. Use whenever the user asks about mocking an API, creating a sandbox, "fake server", WireMock stubs, Prism mocks, MSW (Mock Service Worker), "test fixtures", "stub the API", "mock this
- 0
- Installs
- —
- Rating
- —
- Success rate
- 1
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 826e04f2333e9bab… — run codexguild_scan_skills after installing to verify your local copy.
Static analysis is a first line of defense, not a guarantee. Read the source
SKILL.md
API Mock & Sandbox Skill
Generate mock servers, stubs, fixtures, and sandbox environments for any API.
Mock Strategy Selection
| Scenario | Tool / Approach |
|---|---|
| Frontend dev against unbuilt backend | WireMock / Prism / MSW |
| Unit tests (in-process) | In-memory mock functions |
| Contract testing | Pact (consumer-driven contracts) |
| Postman testing | Postman Mock Server |
| Local development | Prism CLI from OpenAPI spec |
| Record & replay real API | VCR (Python/Ruby), nock recordings |
WireMock Stub Definition
{
"request": {
"method": "GET",
"urlPathPattern": "/api/v1/users/([a-z0-9-]+)"
},
"response": {
"status": 200,
"headers": { "Content-Type": "application/json" },
"jsonBody": {
"id": "{{request.pathSegments.[3]}}",
"name": "Alice Smith",
"email": "alice@example.com",
"created_at": "2024-01-01T00:00:00Z"
}
}
}
WireMock Stateful Scenario
[
{
"scenarioName": "Order flow",
"requiredScenarioState": "Started",
"newScenarioState": "Paid",
"request": { "method": "POST", "url": "/api/v1/orders" },
"response": { "status": 201, "jsonBody": { "id": "ord_123", "status": "pending" } }
},
{
"scenarioName": "Order flow",
"requiredScenarioState": "Paid",
"request": { "method": "GET", "url": "/api/v1/orders/ord_123" },
"response": { "status": 200, "jsonBody": { "id": "ord_123", "status": "paid" } }
}
]
Mock Service Worker (MSW — browser/Node.js)
import { http, HttpResponse } from 'msw';
export const handlers = [
http.get('/api/v1/users', () => {
return HttpResponse.json({
data: [
{ id: 'usr_1', name: 'Alice', email: 'alice@example.com' },
{ id: 'usr_2', name: 'Bob', email: 'bob@example.com' },
],
pagination: { total: 2, page: 1, limit: 20 }
});
}),
http.post('/api/v1/users', async ({ request }) => {
const body = await request.json();
return HttpResponse.json(
{ id: 'usr_new', ...body, created_at: new Date().toISOString() },
{ status: 201 }
);
}),
http.get('/api/v1/users/:id', ({ params }) => {
if (params.id === 'not-found') {
return HttpResponse.json({ error: 'NOT_FOUND' }, { status: 404 });
}
return HttpResponse.json({ id: params.id, name: 'Alice' });
}),
];
Fixture Data Generator
from faker import Faker
import uuid
fake = Faker()
def generate_user(overrides=None):
user = {
"id": str(uuid.uuid4()),
"name": fake.name(),
"email": fake.email(),
"phone": fake.phone_number(),
"address": {
"street": fake.street_address(),
"city": fake.city(),
"country": fake.country_code()
},
"created_at": fake.date_time_this_year().isoformat()
}
return {**user, **(overrides or {})}
def generate_users(count=10):
return [generate_user() for _ in range(count)]
Error Scenario Stubs
Always include these error stubs for every endpoint:
{ "request": { "method": "GET", "url": "/api/v1/users/error-500" },
"response": { "status": 500, "jsonBody": { "error": "INTERNAL_ERROR" } } }
{ "request": { "method": "GET", "url": "/api/v1/users/error-401" },
"response": { "status": 401, "jsonBody": { "error": "UNAUTHENTICATED" } } }
{ "request": { "method": "GET", "url": "/api/v1/users/error-429" },
"response": { "status": 429,
"headers": { "Retry-After": "30" },
"jsonBody": { "error": "RATE_LIMIT_EXCEEDED" } } }
Prism CLI (mock from OpenAPI spec)
# Install
npm install -g @stoplight/prism-cli
# Mock from local spec
prism mock openapi.yaml --port 4010
# Mock from URL
prism mock https://api.example.com/openapi.json
# Validate requests against spec
prism proxy https://api.example.com openapi.yaml
After Completing the API Mocks and Stubs (as requested)
Once the API mocks output is delivered, ask the user:
"Would you like me to help in devising rate limiting strategies for these APIs? (yes/no)"
If the user says yes:
- Check if the api-ratelimiting-helper skill is available in the installed skills list
- If the skill is available:
- Read and follow the instructions in the api-ratelimiting-helper skill
- Use the API information output above as the input
- If the skill is NOT available:
- Inform the user: "It looks like the api-ratelimiting-helper skill isn't installed. You can install it and re-run.
If the user says no:
- End the task here
Files
1- SKILL.md
de2a9fb8e95.3 KB
Agent reviews
0No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.
More from LambdaTest/agent-skills8
Adds automated accessibility (a11y) testing to test suites on TestMu AI cloud by enabling WCAG scans through driver capabilities. Framework-agnostic, works with Selenium, Playwright, and Cypress. Use when user mentions "accessibility", "a11y", "WCAG", "accessibility scan", "accessibility testing". T
Designs AI-powered API features, LLM tool/function definitions, MCP server tool schemas, natural language to API conversion, and agentic API workflows. Use whenever the user asks about "AI calling my API", "function calling schema", "tool definition for LLM", "MCP tools", "natural language API", "AI
Validates whether an API request is correct based on provided inputs (method, URL, headers, body, auth, query params). Use this skill whenever a user wants to check, validate, debug, or verify an API call — including when they paste a curl command, show endpoint details, ask "is this API correct?",
Designs GDPR-compliant API patterns, PCI-DSS field handling, SOC2 audit log schemas, HIPAA data endpoints, and regulatory compliance checklists for any API. Use whenever the user asks about GDPR, data privacy, "right to be forgotten", data retention APIs, PCI compliance for payments, HIPAA for healt
Generates complete, production-ready REST API endpoint specifications for any system or domain the user describes. Use this skill whenever the user asks about API design, API endpoints, REST APIs, API URLs, or says things like "what endpoints do I need for...", "design an API for...", "give me the A
Generate comprehensive, professional API documentation from API designs, endpoint definitions, OpenAPI/Swagger specs, route lists, or raw endpoint descriptions. Use this skill whenever a user provides API endpoints, route definitions, controller code, OpenAPI YAML/JSON, or any structured API design
Provides real-world API endpoint examples and specifications from well-known platforms and domain-specific systems. Use whenever the user asks about APIs for a specific well-known service, wants to integrate with a named platform, or asks "what does the Stripe API look like", "how does the GitHub AP
Designs GraphQL schemas, resolvers, query/mutation/subscription patterns, and protobuf definitions for gRPC services. Use whenever the user asks about GraphQL, "design a GraphQL schema", "write mutations for", "GraphQL subscriptions", "DataLoader pattern", "gRPC service", "protobuf definition", "pro
Related backend skillsscan passed
NestJS architecture patterns for modules, controllers, providers, DTO validation, guards, interceptors, config, and production-grade TypeScript backends. Use when building or reviewing a NestJS backend — modules, providers, DTO validation, guards, or interceptors.
Report browser/API/CLI/job/worker/webhook bugs. (gstack)
This skill should be used when the user wants to "package an MCP server", "bundle an MCP", "make an MCPB", "ship a local MCP server", "distribute a local MCP", discusses ".mcpb files", mentions bundling a Node or Python runtime with their MCP server, or needs an MCP server that interacts with the lo
Guide for upgrading Stripe API versions, webhook endpoints, server-side SDKs, Stripe.js, and mobile SDKs
PostHog integration for server-side Node.js applications using posthog-node
Configure input and output validation with .input() and .output() using Zod, Yup, Superstruct, ArkType, Valibot, Effect, or custom validator functions. Chain multiple .input() calls to merge object schemas. Standard Schema protocol support. Output validation returns INTERNAL_SERVER_ERROR on failure.