api-contract-check

Validate implementations or plans against published API contracts from a registry.

10|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/superluminar-io/pinky-promise --skill api-contract-check-superluminar-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-contract-check
Source: https://github.com/superluminar-io/pinky-promise/tree/main/skills/api-contract-check
Command: npx skills add https://github.com/superluminar-io/pinky-promise --skill api-contract-check-superluminar-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate the current implementation or plan against the published API contracts to ensure every external call adheres to the agreed interface.

Core Features & Use Cases

  • Verifies that code or plans calling external services conform to the registry-published specs.
  • Helps catch mismatches in endpoints, parameters, or payloads before integration.
  • Useful during planning, code reviews, and when implementing new external service integrations.

Quick Start

Invoke api-contract-check during planning or code review to validate against the published API specs in the registry.

Frequently Asked Questions about api-contract-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate code against published API contracts?

You can validate code against published API contracts by checking the implementation or plan against the API registry. This ensures every external service call matches the pinned specs and reports any interface violations or passes accordingly.

When do I need to enforce API spec validation?

API spec validation is needed during planning, code review, and implementation of external service calls. Enforcing the contract ensures that endpoints, parameters, or payloads match the registry spec before integration, catching mismatches early.

How do I check external API calls during code review?

To check external API calls during code review, validate the current implementation against the published API contracts. This enforces public interface commitments and reports any deviations from the agreed registry specifications.

Do I need an API registry to check interface contracts?

Yes, checking interface contracts requires access to an API registry via the API_REGISTRY_REPO. The validation process uses sparse-checkout to fetch pinned specs and bindings, which it then compares against your code to report violations.

What is the best way to catch external API payload mismatches before integration?

The best way to catch external API payload mismatches is to validate your implementation or plan against the published API contracts. This enforces public interface commitments and identifies discrepancies in endpoints, parameters, or payloads before integration.