api-spec-publish

Publish draft API contracts to a centralized versioned registry.

10|Updated Jun 1, 2026

Search Tags:#versioning #publishing #api #openapi #registry #contract #grpc

Ready to run

npx skills add https://github.com/superluminar-io/pinky-promise --skill api-spec-publish

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: api-spec-publish
Source: https://github.com/superluminar-io/pinky-promise/tree/main/skills/api-spec-publish
Command: npx skills add https://github.com/superluminar-io/pinky-promise --skill api-spec-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Publishes a drafted API contract to a centralized, versioned registry to enforce cross-service compatibility and governance.

Core Features & Use Cases

Publish a draft API contract to the registry with a single step
Manage draft bindings and avoid local filesystem exposure
Use guardian decisions to determine version bumps and releases

Quick Start

Publish the current draft API spec to the registry.

Frequently Asked Questions about api-spec-publish

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

FAQPage Schema

How do I publish a draft API contract to a versioned registry?▼

To publish an API contract, the Skill reads from your local registry clone, determines the next version, updates the draft contract, and pushes changes directly to the centralized, versioned registry.

Can I use this to enforce cross-service compatibility for OpenAPI and gRPC specs?▼

Yes, you can enforce cross-service compatibility by publishing OpenAPI, gRPC, and GraphQL spec workflows to the centralized registry, which manages draft bindings and avoids local filesystem exposure.

How do guardian decisions determine version bumps when publishing API specs?▼

Guardian decisions determine version bumps and releases by evaluating branch completion and draft status within the registry workflow before the API spec changes are pushed and published.

What is the best way to manage draft API bindings without exposing local files?▼

Managing draft API bindings without local filesystem exposure is handled by publishing directly to the centralized, versioned registry, ensuring contracts are validated and stored centrally.

Does this API spec publishing process support GraphQL workflow integration?▼

Yes, the API spec publishing process operates within OpenAPI, gRPC, and GraphQL spec workflows, handling branch completion, drafts, and guardian decisions to push contract changes to the registry.