public-api-design

Design public REST and WebSocket APIs with versioning, rate limiting, and key management.

2|Updated Jun 30, 2026
One-click install
npx skills add https://github.com/Canhada-Labs/ceo-orchestration --skill public-api-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: public-api-design
Source: https://github.com/Canhada-Labs/ceo-orchestration/tree/main/.claude/skills/core/public-api-design
Command: npx skills add https://github.com/Canhada-Labs/ceo-orchestration --skill public-api-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill addresses the challenges of designing and implementing public-facing APIs, ensuring robustness, security, and developer-friendly experiences.

Core Features & Use Cases

  • Versioning: Implements API versioning for compatibility and controlled deprecation.
  • Rate Limiting: Enforces tier-based rate limiting to prevent abuse and ensure fair usage.
  • Error Handling: Defines a structured error response contract for better developer experience.
  • Key Management: Manages API keys securely and with user self-service capabilities.
  • Use Case: When building a public API that requires robust key management, comprehensive error handling, and developer-friendly design patterns.

Quick Start

Run the public-api-design skill to set up versioned endpoints with rate limiting for your API.

Frequently Asked Questions about public-api-design

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

FAQPage Schema
How do I implement rate limiting in a public API?

Rate limiting in a public API is implemented by enforcing tier-based request quotas to prevent abuse and ensure fair usage. This approach allows you to control traffic distribution across different consumer tiers while protecting backend resources.

What is the best way to handle API versioning for compatibility?

API versioning for compatibility is managed by implementing versioned endpoints that allow controlled deprecation. This process ensures that existing integrations remain stable when breaking changes are introduced to the public-facing API.

How do I set up self-service API key management for developers?

Self-service API key management is set up by building secure endpoints that allow developers to generate and revoke their own credentials. This mechanism reduces administrative overhead while maintaining security for the public API.

Does this API design approach work with both REST and WebSocket protocols?

Yes, this API design approach works with both REST and WebSocket protocols. It handles both architectural styles with a strong emphasis on security, structured error response contracts, and developer experience.

Why do I need a structured error response contract for my public API?

A structured error response contract is needed for your public API to provide a consistent and predictable developer experience. Defining standard error formats helps third-party developers programmatically handle failures and debug integrations efficiently.