API Route Validator skill for Claude and Codex
Gives a route a pre-release contract check: a checklist covering path shape, auth, parameters, status codes, and rate limits, plus the test cases that prove…
Install it once and Claude or Codex runs it for you. When your request matches, your AI loads the skill, asks for anything it is missing, and works through the template itself. Prefer to fill it in by hand? See the full prompt template.
Download the skill (.zip) · View SKILL.md
When it is used
Use when an API route needs a contract check and test cases before release, covering parameters, auth, status codes, and rate limiting. Do not use for diagnosing a route that is already failing, or generating load tests and performance benchmarks. Related topics: coding, api.
What it will ask you for
- Route path (free text, e.g. "/users/{id}")
- HTTP method (choose one: GET, POST, PUT, DELETE, PATCH)
- Required parameters (longer free text)
- Authentication required (choose one: Yes, No)
- Expected response codes (longer free text)
- Rate limit (requests per minute) (number from 1 to 1000)
How it works
- Write checklist items in request-processing order (path and method, auth, parameters, status codes, rate limit), each phrased as a yes or no question.
- Derive one test case per required parameter, per auth failure mode, per expected status code, and one for the rate limit, so every checklist item has a proving case.
- Fill each case with an ID, the exact input (method, path, headers, body), and the expected status and body shape, so a tester can run it without interpretation.
- Check that no two cases expect different results for the same input and that the happy path appears first.
What you get
Two sections and nothing else: Validation Checklist as a bullet list of yes or no questions, then Sample Test Cases as a table with columns Test ID, Description, Input, Expected Output, happy path first.
What it watches out for
- Testing only the happy path and one generic 400; a missing-parameter case per parameter is what catches the field a refactor dropped.
- Expecting 401 and 403 interchangeably; 401 is a missing or bad credential, 403 is a valid one without permission, and the route must pick one per condition.
- Writing a rate-limit case without stating the window, so the tester cannot tell whether 61 requests in a minute should fail.
How to install
Claude.ai and the Claude desktop app
- Download the skill .zip.
- Open Settings, then Capabilities, and find Skills.
- Choose Upload skill and select the .zip.
- Ask Claude for help with the task. It loads the skill when your request matches.
Claude Code
- Download the skill .zip.
- Unzip it into ~/.claude/skills/ (or .claude/skills/ inside a project).
- Start a new session. Claude Code loads the skill when your request matches.
Codex
- Download the skill .zip.
- Unzip it into ~/.agents/skills/ (or .agents/skills/ inside a project).
- Codex picks it up on its own. Type $ and the skill name to use it, or just ask for the task.
Cursor
- Download the Cursor rule (.mdc).
- Save it in .cursor/rules/ inside your project.
- Cursor's agent applies the rule when your request matches its description.
AGENTS.md (Codex, Cursor, and other coding agents)
- Copy the AGENTS.md section.
- Paste it into AGENTS.md at the root of your repository, creating the file if needed.
- Coding agents that read AGENTS.md follow it when your request fits.