rest-api-expert

Design REST APIs with resource-based endpoints, HTTP status codes, and OpenAPI specs.

Updated Jan 17, 2026
One-click install
npx skills add https://github.com/VanhPoker/VietNamLookmaxing --skill rest-api-expert-vanhpoker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rest-api-expert
Source: https://github.com/VanhPoker/VietNamLookmaxing/tree/main/.agent/skills/rest-api-expert
Command: npx skills add https://github.com/VanhPoker/VietNamLookmaxing --skill rest-api-expert-vanhpoker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design and develop REST APIs with proper resource modeling, consistent endpoints, and reliable documentation to prevent integration issues and versioning pitfalls.

Core Features & Use Cases

  • Endpoint design guidance: convert business requirements into clean, resource-oriented routes with appropriate HTTP methods.
  • HTTP semantics and error handling: apply standard status codes, consistent error envelopes, and robust validation.
  • Versioning and documentation: implement safe versioning strategies and generate OpenAPI specs for downstream clients.
  • Use Case: When starting a new microservice, run this skill to structure the API surface, establish error contracts, and auto-generate docs for teams.

Quick Start

Provide a REST API design brief and generate a ready-to-implement API skeleton that adheres to best practices.

Frequently Asked Questions about rest-api-expert

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

FAQPage Schema
How do I design REST API endpoints with proper HTTP semantics and resource modeling?

REST API design with proper HTTP semantics involves mapping business requirements to resource-oriented routes using appropriate HTTP methods. This skill structures your API surface by enforcing consistent endpoints, correct status codes, and robust validation schemas.

What is the best way to implement REST API versioning and pagination for microservices?

REST API versioning and pagination for microservices require safe versioned routing strategies and consistent pagination schemas. This skill designs these elements to prevent integration issues and ensure scalable data retrieval across public APIs.

How do I generate OpenAPI documentation from my REST API endpoints?

Generating OpenAPI documentation from REST API endpoints establishes clear contracts for downstream clients. This skill auto-generates OpenAPI specs while structuring your API surface, ensuring reliable documentation across microservices.

How do I standardize REST API error handling with consistent status codes?

Standardizing REST API error handling requires applying standard HTTP status codes and consistent error envelopes. This skill evaluates your API to enforce robust validation and reliable error response schemas.

Can I use this to scaffold a new microservice API surface from a design brief?

Yes, you can scaffold a new microservice API surface from a design brief. Provide your REST API requirements to generate a ready-to-implement API skeleton that adheres to best practices and established error contracts.

Why does my REST API integration break during endpoint versioning updates?

REST API integration breaks during endpoint versioning updates often stem from inconsistent routing and poor documentation. This skill prevents versioning pitfalls by implementing safe versioning strategies and generating accurate OpenAPI specs.