Menu
Use when user asks to check API responses, validate request/response contracts, compare API behavior against a spec, or detect schema drift.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when user asks to check browser state, debug page errors, inspect network traffic, take screenshots, automate clicks or form fills, run accessibility or security audits, measure performance, generate tests, or record browser sessions. Trigger phrases: "check my browser", "debug this page", "take a screenshot", "browser errors", "network requests", "automate the browser", "record a test", "accessibility audit", "performance check", "what's on the page".
Use when the user wants a full Kaboom quality audit of a web app or tracked site, with one polished report covering Functionality, UX Polish, Accessibility, Performance, Release Risk, and SEO.
Use when user says "QA my app", "find all bugs", "check my app for problems", "debug my whole app", "what's broken", or wants a comprehensive quality review of their web application.
Use when user asks to automate browser actions, click buttons, fill forms, navigate pages, run a sequence of browser steps, or build a repeatable workflow.
Use when MCP tools fail to connect, user reports "extension not connected", tool calls return errors, or user asks to check their Kaboom setup.
Use when user reports a bug, broken feature, console error, failed network request, or unexpected page behavior that needs investigation.
| name | api-validation |
| description | Use when user asks to check API responses, validate request/response contracts, compare API behavior against a spec, or detect schema drift. |
Use this skill when endpoint behavior, payload shape, or status handling is in question.
Define checks: List each operation with expected request and response constraints.
Collect traffic:
Use observe(network_waterfall) and observe(network_bodies) for matching requests.
Validate contracts:
Run analyze(api_validation) for each operation and capture mismatches.
Check auth and headers: Confirm required cookies/tokens/headers and error-path behavior.
Classify mismatch type: Schema drift, status drift, auth failure, routing mismatch, or serialization issue.
Recommend minimum corrective change: Prefer server/client contract alignment with explicit tests.
operations_checkedmismatchesrisk_levelrecommended_fixfollow_up_tests