agency-api-platform-engineer

Govern API design with contract-first specifications and versioning policies.

Updated Jul 24, 2026
One-click install
npx skills add https://github.com/imMamdouhaboammar/kaku-chatgpt-harness --skill agency-api-platform-engineer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agency-api-platform-engineer
Source: https://github.com/imMamdouhaboammar/kaku-chatgpt-harness/tree/main/.agents/skills/engineering-api-platform-engineer
Command: npx skills add https://github.com/imMamdouhaboammar/kaku-chatgpt-harness --skill agency-api-platform-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the complexity of building and maintaining public or partner-facing APIs, ensuring they remain consistent, backward-compatible, and developer-friendly over long lifecycles.

Core Features & Use Cases

  • Contract-First Design: Enforces OpenAPI/gRPC specifications as the single source of truth before implementation.
  • Lifecycle Governance: Manages versioning, deprecation runways, and breaking change detection to prevent partner disruption.
  • Developer Experience (DX): Automates SDK generation and documentation to ensure parity between the API contract and client libraries.

Quick Start

Use the agency-api-platform-engineer skill to review the current OpenAPI specification for backward compatibility and generate the corresponding SDK documentation.

Frequently Asked Questions about agency-api-platform-engineer

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

FAQPage Schema
How do I enforce backward compatibility for OpenAPI and gRPC specifications?

Backward compatibility for OpenAPI and gRPC specifications is enforced through automated compatibility testing in CI/CD pipelines and strict versioning policies. This approach prevents breaking changes and ensures partner-facing APIs remain stable.

What is contract-first API design and how does it manage SDK generation?

Contract-first API design uses OpenAPI or gRPC specifications as the single source of truth before implementation. This approach automates SDK generation and documentation to ensure strict parity between the API contract and client libraries.

How do I manage API deprecation runways and breaking change detection?

API deprecation runways and breaking change detection are managed through lifecycle governance. This process enforces strict versioning policies to prevent partner disruption when evolving public or partner-facing APIs.

Can I use this approach for API gateway configuration and idempotent operations?

Yes, this approach applies to platform engineering workflows involving API gateway configuration. It satisfies requirements for consistent error semantics and idempent operations within contract-first API development.

What is the best way to automate compatibility testing for public APIs in CI/CD?

The best way to automate compatibility testing for public APIs in CI/CD is by applying contract-first development principles. Using OpenAPI or gRPC specifications as the source of truth allows automated validation of backward compatibility and error semantics.