Skip to content
TrustedSkillsbeta
Back to all skills

Api Contract Review

Checked
decebals·vlatest·backend·MIT

Helps with API, code review as part of agent workflows 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 decebals/claude-code-java --skill api-contract-review -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

decebals

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 decebals/claude-code-java at 0d98fe9bd6.

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

Commit
0d98fe9bd6
Manifest
skills/api-contract-review/SKILL.md
Scanned
2 files, 431 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

What it does

This skill analyzes API contracts (likely OpenAPI/Swagger or similar formats) to identify potential issues, inconsistencies, and areas for improvement. It can help ensure APIs are well-defined, secure, and adhere to best practices. The tool focuses on contract correctness and completeness rather than code generation.

When to use it

  • Before API Release: Validate a new API contract before making it public or integrating with external systems.
  • During API Updates: Ensure changes to an existing API contract don't introduce regressions or break compatibility.
  • For Contract-First Development: Verify the API design is sound and complete before any implementation begins.
  • Automated CI/CD Pipelines: Integrate into automated workflows for continuous API contract validation.

Key capabilities

  • Contract correctness checking
  • Completeness assessment
  • Identification of inconsistencies
  • Best practices adherence verification

Example prompts

  • "Review this OpenAPI specification and identify any potential issues." [followed by the contract content]
  • "Check this API contract for completeness, ensuring all required fields are present." [followed by the contract content]
  • "Analyze this API definition and flag any inconsistencies in data types or parameter names." [followed by the contract content]

Tips & gotchas

The skill requires a valid API contract file (e.g., YAML or JSON) as input. The quality of the review depends on the clarity and accuracy of the provided contract.