API Designer
Jeffallan/claude-skills
Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.
A skill your agent uses when a task adds or changes an HTTP endpoint, its request/response shape, status codes, auth or error format - the request matrix, curl templates and what counts as a…
Install API Contract Testing
$ npx skills add makifbaysal/tasktrooper --skill api-contract-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install makifbaysal/tasktrooper api-contract-testing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/makifbaysal/tasktrooper.git skills-src && mkdir -p .claude/skills && cp -r skills-src/catalog/agents/qa-agent/skills/api-contract-testing .claude/skills/api-contract-testing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "api-contract-testing" agent skill from https://github.com/makifbaysal/tasktrooper/tree/main/catalog/agents/qa-agent/skills/api-contract-testing into .claude/skills/api-contract-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-contract-testing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/makifbaysal/tasktrooper/tree/main/catalog/agents/qa-agent/skills/api-contract-testingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add makifbaysal/tasktrooper --skill api-contract-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install makifbaysal/tasktrooper api-contract-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/makifbaysal/tasktrooper.git skills-src && mkdir -p .agents/skills && cp -r skills-src/catalog/agents/qa-agent/skills/api-contract-testing .agents/skills/api-contract-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "api-contract-testing" agent skill from https://github.com/makifbaysal/tasktrooper/tree/main/catalog/agents/qa-agent/skills/api-contract-testing into .agents/skills/api-contract-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-contract-testing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add makifbaysal/tasktrooper --skill api-contract-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install makifbaysal/tasktrooper api-contract-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/makifbaysal/tasktrooper.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/catalog/agents/qa-agent/skills/api-contract-testing .cursor/skills/api-contract-testing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "api-contract-testing" agent skill from https://github.com/makifbaysal/tasktrooper/tree/main/catalog/agents/qa-agent/skills/api-contract-testing into .cursor/skills/api-contract-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-contract-testing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/makifbaysal/tasktrooper.git --path catalog/agents/qa-agent/skills/api-contract-testing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add makifbaysal/tasktrooper --skill api-contract-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install makifbaysal/tasktrooper api-contract-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/makifbaysal/tasktrooper.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/catalog/agents/qa-agent/skills/api-contract-testing .gemini/skills/api-contract-testing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "api-contract-testing" agent skill from https://github.com/makifbaysal/tasktrooper/tree/main/catalog/agents/qa-agent/skills/api-contract-testing into .gemini/skills/api-contract-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-contract-testing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install makifbaysal/tasktrooper api-contract-testingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add makifbaysal/tasktrooper --skill api-contract-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/makifbaysal/tasktrooper.git skills-src && mkdir -p .github/skills && cp -r skills-src/catalog/agents/qa-agent/skills/api-contract-testing .github/skills/api-contract-testing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "api-contract-testing" agent skill from https://github.com/makifbaysal/tasktrooper/tree/main/catalog/agents/qa-agent/skills/api-contract-testing into .github/skills/api-contract-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-contract-testing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add makifbaysal/tasktrooper --skill api-contract-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install makifbaysal/tasktrooper api-contract-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/makifbaysal/tasktrooper.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/catalog/agents/qa-agent/skills/api-contract-testing .opencode/skills/api-contract-testing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "api-contract-testing" agent skill from https://github.com/makifbaysal/tasktrooper/tree/main/catalog/agents/qa-agent/skills/api-contract-testing into .opencode/skills/api-contract-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-contract-testing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
api-contract-testing- GitHub stars
- 109
- Used in
- 1 other repo
- Token cost
- ~771 tokens
- SKILL.md length
- 331 words
- Files
- 1
- Skills in repo
- 99
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when a task adds or changes an HTTP endpoint, its request/response shape, status codes, auth or error format - the request matrix, curl templates and what counts as a…
- Changes an HTTP endpoint
- SKILL.md covers Contract source, Request template, Per changed endpoint, the matrix and Compatibility, plus 4 more sections
- Calls curl, jq and uvx
- Its request/response shape
What it does
API Contract Testing is an agent skill from makifbaysal/tasktrooper. Use when a task adds or changes an HTTP endpoint, its request/response shape, status codes, auth or error format - the request matrix, curl templates and what counts as a contract break
Its SKILL.md is about 770 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Backend & APIs, covering API design. It works with OpenAPI. The repository describes itself as: Local-first agent platform: board + role agents + agent CLI runs (Claude Code, Cursor, Antigravity, OpenCode) or local and API models (Ollama, LM Studio), all on your own Mac. The licence is Apache-2.0.
When your agent uses it
- Changes an HTTP endpoint
- Its request/response shape
- Error format - the request matrix
- Curl templates and what counts as a contract break
Example prompts
- “/api-contract-testing”
What it can do on your machine
Read from SKILL.md and the folder at commit 09f6258. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
curljquvx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use curl and uvx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
API Contract Testing loads about 771 tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 331 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from makifbaysal/tasktrooper at commit 09f6258, republished under its Apache-2.0 licence (© makifbaysal). 331 words, ~771 tokens.
Download SKILL.mdSave it as
.claude/skills/api-contract-testing/SKILL.md (or your agent's skills folder).- name
- api-contract-testing
- description
- Use when a task adds or changes an HTTP endpoint, its request/response shape, status codes, auth or error format - the request matrix, curl templates and what counts as a contract break
- category
- qa
API Contract Testing
Contract source
The task, its acceptance criteria and the spec document first; then the repo's OpenAPI file or README API docs (the named boot-docs exception). Never the handler source — a contract derived from the implementation only proves the implementation matches itself.
Request template
curl -sS -D "$QA/h.txt" -o "$QA/b.json" -w '%{http_code} %{time_total}s\n' -X POST "$BASE/api/tasks" -H "Authorization: Bearer $TOKEN" -H 'Content-Type: application/json' -d '{"title":"qa-T-12 a"}'; jq . "$QA/b.json" # no jq (stock Windows, some Linux): read_file the body insteadPer changed endpoint, the matrix
One case each, mapped to the category enum:
| Case | Category |
|---|---|
| 2xx happy path | happy_path |
| 400/422 for invalid body, with the error payload shape | negative |
| 401 no token | auth |
| 403 other user's resource (BOLA: create as A, read/update/delete as B) | auth |
| 404 unknown id | negative |
| 409 duplicate where uniqueness is implied | negative |
| 405 wrong method | negative |
extra unknown/privileged field ignored, e.g. "role":"admin" (mass assignment) | auth |
| pagination edges (limit 0, max, max+1) | boundary |
idempotency: PUT/DELETE twice, POST with Idempotency-Key twice when claimed | negative |
| content-type (missing, wrong) | negative |
Compatibility
Existing fields keep their name, type and nullability. A removed or renamed field is a break unless the task explicitly asks for it. Compare against the OpenAPI file, or a request to the same endpoint on stage/the default branch.
Side effects
Verify them the same way backend-manual-testing does — a 2xx with the wrong DB row or missed outbound call is a FAIL, not a pass with a note.
Optional depth: schema fuzzing
Local boot only, and only when the repo ships an OpenAPI file:
uvx schemathesis run <openapi> --url <base> -H "Authorization: Bearer $TOKEN" --include-path-regex '<changed path>' --checks not_a_server_error,status_code_conformance,response_schema_conformance --max-examples 20 --max-failures 5Scope it to the changed paths with --include-path-regex. Never run it against stage or anything shared — it generates many writes.
Worked Example
"POST /tasks title ≤120 chars": happy path (120 chars, 201); empty title (422); 121 chars (422); no auth (401); another user's project (403); duplicate title where unique (409 or 201 per spec); wrong Content-Type (415/400); unknown field is_admin:true ignored (201, field absent from response) — 8 cases, each with its expected code recorded before running it.
Red Flags
- Asserting only the status code and never the body shape.
- Testing authz with the same user for both sides of a BOLA case.
- Fuzzing a shared environment (stage, a shared database).
© makifbaysal, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in catalog/agents/qa-agent/skills/api-contract-testing of makifbaysal/tasktrooper.
Open the folder on GitHubat commit 09f6258
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in makifbaysal/tasktrooper, which our catalogue first saw on October 7, 2026.
Compare with similar skills
API Contract Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| API Contract Testing this skillmakifbaysal/tasktrooper | 109 | 1 repos | ~771 | Automated safety check: Pass | Apache-2.0 | |
| API DesignerJeffallan/claude-skills | 12k | 2 repos | ~2k | Automated safety check: Pass | MIT | |
| Pangolin CRUD Endpointsfosrl/pangolin | 23k | — | ~461 | Automated safety check: Pass | Custom licence | |
| Old Coder API DesignAmazingAng/old-coder | 749 | 1 repos | ~3.4k | Automated safety check: Pass | MIT | |
| Designing APIsCloudAI-X/claude-workflow-v2 | 1.4k | 2 repos | ~1.2k | Automated safety check: Pass | MIT | |
| API Surface Reviewpolarsource/polar | 10k | — | ~1.3k | Automated safety check: Pass | MIT |
Similar skills
Pangolin CRUD Endpoints
fosrl/pangolin
Use whenever asked to add, create, or scaffold a CRUD endpoint, router, or entity in this repo's server (create/list/get/update/delete handlers, new…
Old Coder API Design
AmazingAng/old-coder
Reviews or designs an HTTP/JSON API's endpoints, auth, pagination, versioning and deprecations, guarding against inventing a bespoke interface or silently breaking consumers.
Designing APIs
CloudAI-X/claude-workflow-v2
Designs REST and GraphQL APIs including endpoints, error handling, versioning, and documentation.
API Surface Review
polarsource/polar
Review changes to Polar's API contract — Pydantic schemas, FastAPI endpoints, OpenAPI output and the generated SDKs.
API Contract
ChenyCHENYU/Robot_Admin
A skill your agent uses when: generating TypeScript API layer (type definitions + request functions) from page-spec JSON or Swagger/OpenAPI docs.
More from makifbaysal/tasktrooper
All 99 skills in this repoAcceptance Criteria Gwt
makifbaysal/tasktrooper
A skill your agent uses when writing acceptance criteria for a task - express each as an observable Given/When/Then that QA can execute, including negative cases
Accessibility Check
makifbaysal/tasktrooper
A skill your agent uses when a task changes any screen, form, dialog, menu or control - Lighthouse/axe scan of the changed screens, a keyboard walk, and the thresholds that fail a task
Analiz Gate
makifbaysal/tasktrooper
A skill your agent uses when deciding whether a request needs an analiz task before implementation - the conditions that require the architect's analysis versus going straight to implementation
Analiz HTML Report
makifbaysal/tasktrooper
A skill your agent uses when you write or revise the analiz deliverable - the ONE self-contained HTML report (spec and plan as sections) a human reviews passage by passage
Analiz Human Review Gate
makifbaysal/tasktrooper
A skill your agent uses when you finish an analiz report - the human must approve the analysis before any implementation task is created, via the analizreview column
Android Compose Patterns
makifbaysal/tasktrooper
A skill your agent uses when building native Android with Jetpack Compose - stateless composables, state hoisting, ViewModel-owned state, edge-to-edge, predictive back, adaptive layout, atomic…
Related
Works with
Categories
Questions about API Contract Testing
What does API Contract Testing do?
A skill your agent uses when a task adds or changes an HTTP endpoint, its request/response shape, status codes, auth or error format - the request matrix, curl templates and what counts as a…. API Contract Testing is an agent skill from makifbaysal/tasktrooper.
When should I use API Contract Testing?
API Contract Testing fits situations like: changes an HTTP endpoint; its request/response shape; error format - the request matrix; curl templates and what counts as a contract break.
How do I install API Contract Testing in Claude Code?
Run `npx skills add makifbaysal/tasktrooper --skill api-contract-testing -a claude-code`. Or copy the skill folder (catalog/agents/qa-agent/skills/api-contract-testing in makifbaysal/tasktrooper) into .claude/skills/api-contract-testing in your project. Claude Code loads it when a task matches its description.
How do I install API Contract Testing in Codex?
Run `npx skills add makifbaysal/tasktrooper --skill api-contract-testing -a codex`. Or copy the skill folder (catalog/agents/qa-agent/skills/api-contract-testing in makifbaysal/tasktrooper) into .agents/skills/api-contract-testing in your project. Codex loads it when a task matches its description.
Can I use API Contract Testing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add makifbaysal/tasktrooper --skill api-contract-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/api-contract-testing, .gemini/skills/api-contract-testing, .github/skills/api-contract-testing and .opencode/skills/api-contract-testing in your project.
What does API Contract Testing need to run?
Going by SKILL.md and its folder, API Contract Testing needs the command-line tools its instructions call (curl, jq and uvx).
Does API Contract Testing access the network?
SKILL.md contains no URLs. Its commands use curl and uvx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is API Contract Testing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does API Contract Testing use?
API Contract Testing is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does API Contract Testing use?
About 771 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to API Contract Testing?
Skills that share tags, products or a category with API Contract Testing: API Designer (Jeffallan/claude-skills, 12k stars), Pangolin CRUD Endpoints (fosrl/pangolin, 23k stars), Old Coder API Design (AmazingAng/old-coder, 749 stars) and Designing APIs (CloudAI-X/claude-workflow-v2, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains API Contract Testing?
makifbaysal (a GitHub user) maintains it in makifbaysal/tasktrooper, which has 109 GitHub stars. The repository holds 99 skills in this directory. The repository was last updated on October 7, 2026.
Source: makifbaysal/tasktrooper on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.