Best fit
Lints an OpenAPI spec and diffs two versions to catch breaking API changes before they reach consumers.
// api
OpenAPI Contract Guard
Lint an OpenAPI spec and diff two versions to catch breaking API changes before they reach consumers.
What it flags
- Within a spec: missing operationId, responses with no schema, untyped params, operations with no security, unbounded arrays or strings.
- Across versions: removed paths and operations.
- A removed response code.
- A parameter becoming required.
- Narrowed types and removed enum values.
- Removed response fields.
How to run
It analyzes JSON specs; convert YAML to JSON first (the agent can do that). Read-only.
Good to know
Heuristic structural diff. Semantic compatibility and ref-heavy specs may need a manual pass.
// choose with context
Is OpenAPI Contract Guard the right skill?
It returns
Lints an OpenAPI spec and diffs two versions to catch breaking API changes before they reach consumers.
Do not use it as
Do not treat a successful run as proof beyond the supplied files, declared scope, and evidence the skill actually checked.
Compatibility, access, version, and licence
- Reads or accesses
- Only the files or context you deliberately provide; review the listing before granting additional access.
- Compatibility
- Agents that read the open SKILL.md format. Verify runtime and service requirements at the purchase or install destination.
- Version
- Verify the current package version at the linked destination.
- Licence
- Review the package licence and seller terms at the linked destination.
Questions
What is the wedge?
Version-to-version breaking-change detection, the thing that pages a team when consumers break.
Does it change anything?
No. It is read-only and flags issues for you to act on.
Break nothing your consumers depend on.
Current price and purchase option are shown on Agensi. Instant download. Works with any agent that reads SKILL.md.
Get OpenAPI Contract Guard on Agensi