api-testing
Use when testing HTTP endpoints, probing URLs for status and headers, or running declarative API test suites from plain text files
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill api-testing --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 Testing ## When to Use - Testing REST API endpoints for correct responses - Writing declarative, repeatable HTTP test suites - Chaining HTTP requests (authenticate → create → verify) - Probing multiple URLs for availability, status codes, or headers - Validating response bodies, headers, and status codes with assertions ## Tools | Tool | Purpose | Structured output | |------|---------|------
What does the api-testing skill do?
Use when testing HTTP endpoints, probing URLs for status and headers, or running declarative API test suites from plain text files
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill api-testing --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 jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 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.