api-mock-helper
>
pinned to #54824d6updated 2 weeks ago
Ask your AI client: “install skills/api-mock-helper”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/api-mock-helpermetahub onboarded this repo on the author's behalf.
If you own github.com/LambdaTest/agent-skills on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
325
Last commit
2 weeks ago
Latest release
published
About this skill
Pulled from SKILL.md at publish time.
Generate mock servers, stubs, fixtures, and sandbox environments for any API.
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.54824d6· 2 weeks ago
Documentation
32Description qualitywarn
8 words · 52 chars — skills use the description as their trigger; aim higher — manifest description is empty; graded the GitHub repo description instead
Aim for 15+ words and include trigger phrases like “use this skill when …”.
README is present and substantial
6,607 chars · 7 sections · 6 code blocks
Tags / topics declaredwarn
No manifest tags and no GitHub repo topics
Add tags to the manifest (or GitHub topics on the repo) so the registry's search and category filters surface this artifact.
README has usage / example sections
found: Getting Started
Homepage / docs URL declared
https://agentskillsforall.com/
Release history
1- releasecurrent54824d6warn2 weeks ago
Contents
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": "[email protected]",
"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: '[email protected]' },
{ id: 'usr_2', name: 'Bob', email: '[email protected]' },
],
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
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/api-mock-helper