Skip to content
TrustedSkillsbeta
Back to all skills

Api Testing

Checked
sgcarstrends·vlatest·testing·MIT

Helps with API, testing as part of testing, debugging, and quality assurance workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add motormetrics/motormetrics --skill api-testing -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

sgcarstrends

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

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 sgcarstrends/sgcarstrends at d852d8c519.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
d852d8c519
Manifest
.agents/skills/api-testing/SKILL.md
Scanned
2 files, 272 lines
Copies in repo
2 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to perform automated testing on Application Programming Interfaces (APIs). It validates endpoint functionality, checks response formats, and ensures data integrity across various network services.

When to use it

  • Verifying that new API endpoints return expected status codes and data structures before deployment.
  • Running regression tests to ensure recent code changes haven't broken existing integrations.
  • Simulating user interactions with backend services to identify latency or failure points.
  • Validating authentication tokens and permission levels across different API scopes.

Key capabilities

  • Automated execution of test cases against live or mock API endpoints.
  • Detailed reporting on request parameters, response bodies, and error logs.
  • Validation of data schemas and JSON payloads returned by services.
  • Support for various HTTP methods (GET, POST, PUT, DELETE) in testing workflows.

Example prompts

  • "Run a suite of tests on the /users endpoint to check if it correctly returns 401 errors for unauthenticated requests."
  • "Validate that the payment processing API returns a valid JSON response with a transaction_id field upon successful submission."
  • "Simulate a high-volume load test on the inventory update API and report any timeout occurrences."

Tips & gotchas

Ensure you have valid API keys or access tokens configured before running tests against production environments to avoid triggering rate limits. Always review error logs generated during testing to distinguish between network failures and logic errors in your code.