api-expert

Guide REST, GraphQL, and gRPC API design with security and versioning.

3|1|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/Probably-Group/Dev-AID --skill api-expert-probably-group
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: api-expert
Source: https://github.com/Probably-Group/Dev-AID/tree/main/.dev-aid/skills/expert/api-expert
Command: npx skills add https://github.com/Probably-Group/Dev-AID --skill api-expert-probably-group

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you design API architectures that stay secure and maintainable while meeting practical cross-cutting requirements like versioning, rate limiting, and documentation.

Core Features & Use Cases

  • API architecture & patterns: RESTful resource modeling (methods, nesting, naming) and cross-cutting concerns across endpoints.
  • Security guardrails: authorization checks, SSRF defenses, TLS requirements, rate limiting, strict CORS, and safe error handling.
  • Operational readiness: API versioning strategies, OpenAPI documentation scaffolding, and pagination/auth logging checklists for production.

Use Case: You are starting a new backend for a SaaS app and need to decide REST vs GraphQL vs gRPC boundaries, lock down auth/authorization, define v1/v2 versioning, set rate limits, and produce OpenAPI-ready endpoint specs without accidentally introducing BOLA, SSRF, or permissive CORS.

Quick Start

Tell the AI: "Design my API style and versioning strategy, including REST resource conventions, OpenAPI documentation approach, pagination, and security requirements like authorization, rate limiting, SSRF protection, strict CORS, and non-leaky errors—then provide a production checklist before code generation."

Frequently Asked Questions about api-expert

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

FAQPage Schema
How do I design a secure API architecture with proper versioning and rate limiting?▼

Secure API architecture requires RESTful resource modeling, strict CORS, TLS, rate limiting safeguards, and a defined v1/v2 versioning strategy to prevent breaking changes while maintaining operational readiness.

What is the best way to choose between REST, GraphQL, and gRPC for my backend services?▼

Choosing between REST, GraphQL, and gRPC depends on your client interaction patterns; REST suits standard resource modeling, GraphQL optimizes nested data fetching, and gRPC handles internal high-performance service-to-service communication.

How do I structure OpenAPI documentation for endpoints with pagination and auth logging?▼

Structuring OpenAPI documentation involves defining consistent endpoint specifications, incorporating pagination parameters, and detailing authentication mechanisms alongside logging checklists to ensure production operational readiness.

How can I prevent BOLA, SSRF, and permissive CORS vulnerabilities when creating new endpoints?▼

Preventing BOLA, SSRF, and permissive CORS requires implementing strict authorization checks on resources, validating external URLs to block server-side request forgery, and configuring strict cross-origin sharing policies.

Does my API gateway need specific configurations for error handling and non-leaky responses?▼

Yes, an API gateway requires safe error handling configurations to ensure non-leaky responses, preventing internal system details from exposing stack traces or sensitive operational data to external clients.