Api Testing
CheckedHelps with API, testing as part of testing, debugging, and quality assurance workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add serkan-ozal/browser-devtools-skills --skill api-testing -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
serkan-ozal
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned serkan-ozal/browser-devtools-skills at 62b9f7990f.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 62b9f7990f
- Manifest
- skills/api-testing/SKILL.md
- Scanned
- 1 file, 179 lines
About this skill
What it does
This skill allows an AI agent to perform API testing using browser developer tools. It can execute requests, inspect responses (including headers and body), and validate data against expected outcomes. The tool facilitates debugging and verifying the functionality of web APIs directly within a browser environment.
When to use it
- Debugging API integrations: Troubleshoot issues when an application isn't receiving or processing data correctly from an external API.
- Validating API endpoints: Ensure that newly developed or modified API endpoints return the expected data and status codes.
- Testing authentication flows: Verify that API requests are properly authenticated and authorized.
- Analyzing API responses: Inspect detailed response information, such as headers and body content, to understand API behavior.
Key capabilities
- Execute HTTP requests (GET, POST, PUT, DELETE, etc.)
- Inspect request and response headers
- View raw response bodies (JSON, XML, HTML)
- Validate data within responses
Example prompts
- "Send a GET request to
https://example.com/api/usersand show me the response." - "Make a POST request to
https://example.com/api/productswith this JSON payload:{ "name": "New Product", "price": 29.99 }." - “Inspect the headers of the response from
https://api.example.com/data.”
Tips & gotchas
This skill requires familiarity with browser developer tools and API request structures. The agent will need clear instructions regarding the URL, method (GET, POST, etc.), and any necessary data payloads for successful execution.