Use Yaak
mountain-loop/yaak
A skill your agent uses when the user mentions Yaak, a Yaak workspace, or the yaak command, or asks to call, hit, or smoke test HTTP/REST endpoints, save or organize API requests for reuse or manual…
A skill your agent uses when you need to design API test plans or cases for REST, GraphQL, or gRPC interfaces; triggers include API testing and API test cases.
Install API Testing
$ npx skills add naodeng/awesome-qa-skills --skill api-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install naodeng/awesome-qa-skills api-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/naodeng/awesome-qa-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/en/testing-types/api-testing .claude/skills/api-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-testing" agent skill from https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/api-testing into .claude/skills/api-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-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/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/api-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 naodeng/awesome-qa-skills --skill api-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install naodeng/awesome-qa-skills api-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/naodeng/awesome-qa-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/en/testing-types/api-testing .agents/skills/api-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-testing" agent skill from https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/api-testing into .agents/skills/api-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-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 naodeng/awesome-qa-skills --skill api-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install naodeng/awesome-qa-skills api-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/naodeng/awesome-qa-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/en/testing-types/api-testing .cursor/skills/api-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-testing" agent skill from https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/api-testing into .cursor/skills/api-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-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/naodeng/awesome-qa-skills.git --path skills/en/testing-types/api-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 naodeng/awesome-qa-skills --skill api-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install naodeng/awesome-qa-skills api-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/naodeng/awesome-qa-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/en/testing-types/api-testing .gemini/skills/api-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-testing" agent skill from https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/api-testing into .gemini/skills/api-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-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 naodeng/awesome-qa-skills api-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 naodeng/awesome-qa-skills --skill api-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/naodeng/awesome-qa-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/en/testing-types/api-testing .github/skills/api-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-testing" agent skill from https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/api-testing into .github/skills/api-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-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 naodeng/awesome-qa-skills --skill api-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 naodeng/awesome-qa-skills api-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/naodeng/awesome-qa-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/en/testing-types/api-testing .opencode/skills/api-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-testing" agent skill from https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/api-testing into .opencode/skills/api-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-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-testing- GitHub stars
- 245
- Token cost
- ~636 tokens
- SKILL.md length
- 310 words
- Files
- 39 (incl. scripts, references)
- Skills in repo
- 22
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
A skill your agent uses when you need to design API test plans or cases for REST, GraphQL, or gRPC interfaces; triggers include API testing and API test cases.
- Works in 4 steps: Read and follow the main prompt listed… → Add only project context that changes… → If input is incomplete, return a usable… → …
- You need to design API test plans
- SKILL.md covers When to Use, Workflow, Core Constraints and Progressive Disclosure, plus 2 more sections
- GRPC interfaces
What it does
API Testing is an agent skill from naodeng/awesome-qa-skills. Use this skill when you need to design API test plans or cases for REST, GraphQL, or gRPC interfaces; triggers include API testing and API test cases.
Its SKILL.md is about 640 tokens, which your agent loads only when the skill is triggered. The skill folder holds 43 other files, including scripts and reference files (for example `README.md`, `agents/openai.yaml` and `evals/cases/basic-success.yaml`).
It sits in Testing & QA, covering API testing. It works with gRPC and GraphQL. The repository describes itself as: Awesome QA Skills is an open-source AI-native Quality Engineering skill system that helps engineering teams reason about, design, execute, evaluate, and continuously improve…
When your agent uses it
- You need to design API test plans
- GRPC interfaces
- Triggers include API testing and API test cases
Example prompts
- “/api-testing”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Read and follow the main prompt listed under Progressive disclosure (coverage, structure, quality bar).
- Add only project context that changes the result: scope, environment, constraints, risks, dependencies, expected deliverable.
- If input is incomplete, return a usable first draft and explicitly mark assumptions and gaps.
- Default to Markdown; switch formats only when the user asks.
What it can do on your machine
Read from SKILL.md and the folder at commit 52c4eaf. 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
Ships 1 file in scripts/, which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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 Testing loads about 636 tokens when it runs, and up to ~1.3k if it reads all its reference files. Until then it costs about 41 tokens; SKILL.md has 310 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); the scripts in this folder are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 310 words (~636 tokens).
“Chinese version： See the corresponding Chinese skill.”
- name
- api-testing
Files
SKILL.md and 38 other files (scripts, references) in skills/en/testing-types/api-testing of naodeng/awesome-qa-skills.
- SKILL.md
- README.md
- agents/openai.yaml
- evals/cases/basic-success.yaml
- evals/cases/edge-incomplete-input.yaml
- evals/cases/edge-risk-priority.yaml
- evals/eval.yaml
- output-formats.md
- output-templates/template-csv.csv
- output-templates/template-excel.tsv
- output-templates/template-json.json
- output-templates/template-markdown.md
- output-templates/template-word.md
- output-templates/template-xmind.md
- prompts/api-testing.md
- quick-start.md
- … and 23 more
Open the folder on GitHubat commit 52c4eaf
Compare with similar skills
API 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 Testing this skillnaodeng/awesome-qa-skills | 245 | — | ~636 | Automated safety check: Pass | Custom licence | |
| Use Yaakmountain-loop/yaak | 19k | — | ~1.9k | Automated safety check: Pass | MIT | |
| API Testingpetrkindlmann/qa-skills | 165 | — | ~2.7k | Automated safety check: Pass | MIT | |
| API Testingcosmicstack-labs/mercury-agent-skills | 476 | — | ~449 | Automated safety check: Pass | MIT | |
| API Testingfugazi/test-automation-skills-agents | 247 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Playwright E2E Testingfugazi/test-automation-skills-agents | 247 | — | ~3.2k | Automated safety check: Pass | MIT |
Similar skills
API Testing
petrkindlmann/qa-skills
Test REST and GraphQL APIs with Playwright APIRequestContext, Supertest, or standalone HTTP clients.
API Testing
cosmicstack-labs/mercury-agent-skills
REST and GraphQL testing, Postman/Insomnia patterns, contract testing, schema validation, and monitoring
API Testing
fugazi/test-automation-skills-agents
Test REST and GraphQL endpoint contracts using Playwright request fixture (TypeScript) or REST Assured (Java).
Playwright E2E Testing
fugazi/test-automation-skills-agents
Author and maintain versioned Playwright (@playwright/test) TypeScript UI specs for browser user flows.
API Tester
RightNow-AI/openfang
API testing expert for curl, REST, GraphQL, authentication, and debugging
More from naodeng/awesome-qa-skills
All 22 skills in this repoAccessibility Testing
naodeng/awesome-qa-skills
A skill your agent uses when you need to design accessibility testing against WCAG, keyboard navigation, and assistive technology scenarios; triggers include accessibility testing and a11y testing.
API Test Bruno
naodeng/awesome-qa-skills
A skill your agent uses when you need to parse multi-format API definitions and generate Bruno collections for executable regression; triggers include Bruno collections and Bruno API testing.
API Test Pytest
naodeng/awesome-qa-skills
A skill your agent uses when you need to parse multi-format API definitions and generate Pytest API automation; triggers include Pytest API tests and API automation with Pytest.
API Test Restassure
naodeng/awesome-qa-skills
A skill your agent uses when you need to parse multi-format API definitions and generate Rest Assured Java test classes; triggers include Rest Assured, RestAssured, and Java API automation.
API Test Supertest
naodeng/awesome-qa-skills
A skill your agent uses when you need to parse multi-format API definitions and generate executable Supertest scripts; triggers include Supertest, Node.js API testing, and Supertest automation.
Automation Testing
naodeng/awesome-qa-skills
A skill your agent uses when you need to design automation testing approaches using patterns like POM, data-driven testing, or BDD; triggers include automation testing and test automation strategy.
Related
Categories
Questions about API Testing
What does API Testing do?
A skill your agent uses when you need to design API test plans or cases for REST, GraphQL, or gRPC interfaces; triggers include API testing and API test cases. API Testing is an agent skill from naodeng/awesome-qa-skills. Use this skill when you need to design API test plans or cases for REST, GraphQL, or gRPC interfaces; triggers include API testing and API test cases.
When should I use API Testing?
API Testing fits situations like: you need to design API test plans; GRPC interfaces; triggers include API testing and API test cases.
How do I install API Testing in Claude Code?
Run `npx skills add naodeng/awesome-qa-skills --skill api-testing -a claude-code`. Or copy the skill folder (skills/en/testing-types/api-testing in naodeng/awesome-qa-skills) into .claude/skills/api-testing in your project. Claude Code loads it when a task matches its description.
How do I install API Testing in Codex?
Run `npx skills add naodeng/awesome-qa-skills --skill api-testing -a codex`. Or copy the skill folder (skills/en/testing-types/api-testing in naodeng/awesome-qa-skills) into .agents/skills/api-testing in your project. Codex loads it when a task matches its description.
Can I use API 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 naodeng/awesome-qa-skills --skill api-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-testing, .gemini/skills/api-testing, .github/skills/api-testing and .opencode/skills/api-testing in your project.
What does API Testing need to run?
SKILL.md names no scripts, command-line tools or credentials: API Testing is instructions for the agent only.
Does API Testing access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is API 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does API Testing use?
API Testing has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does API Testing use?
About 636 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 673 tokens, read only when the agent opens those files.
What are the alternatives to API Testing?
Skills that share tags, products or a category with API Testing: Use Yaak (mountain-loop/yaak, 19k stars), API Testing (petrkindlmann/qa-skills, 165 stars), API Testing (cosmicstack-labs/mercury-agent-skills, 476 stars) and API Testing (fugazi/test-automation-skills-agents, 247 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains API Testing?
naodeng (a GitHub user) maintains it in naodeng/awesome-qa-skills, which has 245 GitHub stars. The repository holds 22 skills in this directory. The repository was last updated on September 26, 2026.
Source: naodeng/awesome-qa-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.