- Home
- Skills
- APIs & Backend
- ContractTrace — OpenAPI Implementation Drift Desk
More screenshots
Works with the AI Agents you already use
ContractTrace — OpenAPI Implementation Drift Desk
Reconcile OpenAPI contracts against handlers, validation and actual response fixtures.
$12
ContractTrace — OpenAPI Implementation Drift Desk
Example session with this skill installed
Run ContractTrace — OpenAPI Implementation Drift Desk as an evidence-first preflight. This is a representative, hypothetical test case: The contract marks customer.email required but POST /customers handler permits null and returns 201. The materials I have available are: OpenAPI YAML/JSON specification; route handler source; request/response fixtures and tests. Tell me what is evidenced, what is missing, which claims must be held, the exact corrections, and a clean verification plan. Do not claim you opened a file or performed a live run unless one is actually supplied.
- Read your context and instructions
- Compiled the contracttrace
REPRESENTATIVE EXAMPLE — NOT A LIVE RUN
PREFLIGHT: HOLD / VERIFY BEFORE ACTING. Task: Reconcile OpenAPI contracts against handlers, validation and actual response fixtures.
Scenario supplied by buyer: The contract marks customer.email required but POST /customers handler permits null and returns 201.
-
MATERIAL FINDING (HIGH): The stated contract and shown handler validation disagree on a required field. The case describes a potential issue; no underlying account, file or production service has been accessed by this illustrative demo.
-
TRACEABILITY MATRIX
- Claimed behavior: The contract marks customer.email required but POST /customers handler permits null and returns 201.
- Critical evidence sources: OpenAPI YAML/JSON specification, route handler source, request/response fixtures and tests.
- Status: NOT VERIFIED from primary artifacts in this example. A real invocation must attach the files or authorize a read-only source inspection and record exact references.
- CHECKS THE SKILL WILL RUN
- Index paths, methods, status codes, required fields and schema version across contract and code.
- Map observed handlers to documented routes, accounting for base paths and versioned routers.
- Flag required/nullable type changes and missing error response documentation with exact file links.
- Distinguish static suspicion from verified integration-test failures using recorded fixtures.
- Generate minimal schema or implementation fixes plus compatibility and consumer-test plan.
-
CORRECTION TO PROPOSE
Confirm intended contract with API owner; either reject null with a tested 4xx or update documented schema and clients. Do not present this as implemented until the seller/developer actually applies the change and reviews the result. -
REPRODUCTION / ACCEPTANCE TEST
Run positive/negative fixtures against a sandbox endpoint and compare decoded response shapes. Capture the before/after witness (paths, commands, timestamp, observed outcome), distinguish a script signal from a working end-to-end product, and do not invent a PASS. -
SCOPE LIMIT
Cannot assert production traffic compatibility without real clients and test evidence.
Final handoff: a clear evidence-linked issue list, copy-ready proposed changes where appropriate, a prioritized checklist, and a statement of exactly which tests were and were not run.
Connects securely to your tools. The creator never sees your data.
About this skill
ContractTrace — OpenAPI Implementation Drift Desk
Reconcile OpenAPI contracts against handlers, validation and actual response fixtures.
What you receive
- A ready-to-install skill with a repeatable, evidence-first procedure.
- A source-to-claim discrepancy matrix, severity tags and specific corrective actions.
- A clearly separated verification checklist and unknowns register.
- A representative worked example; it is not passed off as a live customer run.
Example issue
The contract marks customer.email required but POST /customers handler permits null and returns 201.
Trust boundary
Cannot assert production traffic compatibility without real clients and test evidence.
No paid API subscription is bundled. The agent can inspect materials supplied by the buyer in its supported environment. Access to private services is never presumed.
Cannot assert production traffic compatibility without real clients and test evidence.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 8 days ago
Permissions
File Scopes
No production changes or account access without owner authorization.