api-test-plan
Plan tests for an API endpoint or service — functional, negative, and contract. Use when asked to test an API, write API test cases, plan REST/GraphQL endpoint testing, or validate an API contract. Produces an API test plan — per-endpoint cases (status codes, schema, auth, validation, errors), boundary/negative cases, contract checks, and non-functional notes — so the API is verified beyond the happy 200.
npx skills add mohitagw15856/pm-claude-skills --skill api-test-plan --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# API Test Plan Skill APIs fail in specific, testable ways: wrong status codes, schema drift, missing auth checks, sloppy validation, unhelpful errors. This skill plans the tests that catch them — per endpoint, across the response codes and the error paths, with contract checks so the API keeps its promises to clients. It tests the whole behaviour, not just the happy `200`. ## Working from a brief Given an endpoint or an API description, **produce the test plan anyway** — infer the likely parameters, responses, auth model, and error cases, labelling assumptions. Always include auth, validation, and negative cases. Never hand back a question instead of a plan. ## Required Inputs Ask for these only if they aren't already provided (else infer and label): - **The API** — REST/GraphQL, the endpoints/operations, and what they do. - **Contract** — request/response schemas, parameters, status codes (or an OpenAPI/spec if available). - **Auth & rules** — the auth model (token/scopes/roles), rate limits, and validation rules. - **Dependencies & data** — downstream services, and the data/state needed to test. ## Output Format ### API Test Plan: [API / endpoint] **Per endpoint**, a set of case
- Working from a brief
- Required Inputs
- Output Format
- API Test Plan: [API / endpoint]
- Quality Checks
- Anti-Patterns
- Based On
What does the api-test-plan skill do?
Plan tests for an API endpoint or service — functional, negative, and contract. Use when asked to test an API, write API test cases, plan REST/GraphQL endpoint testing, or validate an API contract. Produces an API test plan — per-endpoint cases (status codes, schema, auth, validation, errors), boundary/negative cases, contract checks, and non-functional notes — so the API is verified beyond the happy 200.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill api-test-plan --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.