Skip to content
TrustedSkillsbeta
Back to all skills

Api Contract Testing

Checked
aj-geddes·vlatest·backend·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 aj-geddes/useful-ai-prompts --skill api-contract-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

aj-geddes

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 aj-geddes/useful-ai-prompts at 3f5182cfd7.

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

Commit
3f5182cfd7
Manifest
skills/api-contract-testing/SKILL.md
Scanned
9 files, 696 lines
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

api-contract-testing

What it does

This skill automates the verification of API contracts by generating test cases and validating responses against expected schemas. It ensures that your backend services adhere to defined specifications before integration, catching breaking changes early in the development cycle.

When to use it

  • You need to validate that a new API endpoint returns data matching a specific JSON schema.
  • Your team is refactoring an existing service and you must ensure backward compatibility with current clients.
  • You want to generate automated regression tests for an OpenAPI or Swagger definition without writing manual code.
  • You are integrating third-party services and need to verify their actual behavior matches the documented contract.

Key capabilities

  • Automatically generates test cases based on provided API documentation or schemas.
  • Validates API responses against expected structures and data types.
  • Identifies discrepancies between actual service behavior and defined contracts.
  • Supports various common API specification formats for broad compatibility.

Example prompts

  • "Generate a set of unit tests for this OpenAPI 3.0 specification to verify the /users endpoint returns valid JSON."
  • "Check if the current implementation of the payment API matches the provided contract and list any breaking changes found."
  • "Create validation rules to ensure the response from the inventory service adheres to the defined schema constraints."

Tips & gotchas

Ensure your API documentation is up-to-date, as the skill relies heavily on accurate definitions to generate meaningful tests. This tool complements but does not replace full end-to-end integration testing; it focuses specifically on contract adherence rather than business logic or external dependencies.