← StubEngineCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to StubEngine
Snapshot Sep 30, 2026 · 22:56 UTC · version 1.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "create-api-mock",
"description": "Use this skill to quickly create a live API mock from a natural language description. It guides you through selecting an organization and defining the mock behavior.",
"included_files": [],
"skill_md_contents": "---\nname: create-api-mock\ndescription: Use this skill to quickly create a live API mock from a natural language description. It guides you through selecting an organization and defining the mock behavior.\n---\n\n### Instructions\n\nWhen the user wants to create a mock:\n\n1. **Identify the User's Goal**: Understand the API behavior they want to mock (method, path, status, body).\n2. **List Organizations**: Call `list_organizations` to show the user which workspaces they have access to.\n3. **Confirm Organization**: Ask the user to select an organization from the list if they haven't specified one. Use the `id` (as `orgId`) and `slug` (as `orgSlug`) from the selected organization.\n4. **Draft Mapping**: Create a WireMock JSON mapping based on the user's description.\n - Include `request` (method, url, urlPattern, or urlPathTemplate).\n - Include `response` (status, body, jsonBody, or headers).\n5. **Create Endpoint**: Call `create_endpoint` with the `orgId`, `orgSlug`, and the `mapping`.\n6. **Report Success**: Provide the user with the `url` of the new live mock and confirm it is ready for use.\n\n### Examples\n\n- \"Create a GET /health mock that returns 200 OK.\"\n- \"I need a mock for POST /orders that returns a 201 Created status and a JSON body with an order ID.\"\n"
}SHA-256: 6a1c0895124d0a01ebcbeeabdd3e69e2bcd03a8d35bc6eb3fea343be9ce10302