Design RESTful and GraphQL APIs following best practices. Use when creating new APIs, refactoring existing endpoints, or documenting API specifications. Handles OpenAPI, REST, GraphQL, versioning.
REST resource naming, HTTP methods, and response codes
Plural resource names
100%
100%
Noun-based paths
50%
100%
Logical resource nesting
100%
100%
URL versioning
87%
100%
Correct HTTP method usage
100%
100%
201 for creation
100%
100%
204 for deletion
100%
62%
404 and 400 codes
100%
100%
Location header on 201
0%
0%
Timestamps in response
100%
100%
Structured error format
100%
100%
Error details field
0%
100%
Pagination response format and OpenAPI 3.0 documentation
OpenAPI 3.0 version
100%
100%
Required top-level sections
100%
100%
Pagination query params
75%
100%
Pagination metadata in response
70%
100%
Pagination links in response
0%
100%
JWT bearer auth defined
100%
100%
Auth applied to write endpoints
100%
100%
Reusable $ref schemas
100%
100%
Timestamps in schema
100%
100%
Sorting query parameter
100%
100%
Filter query parameters
100%
100%
Field selection support
0%
0%
Batch operations, field selection, filtering, and sorting patterns
Batch endpoint path
100%
100%
Batch operations array
100%
100%
Batch supports multiple actions
100%
100%
Field selection via fields param
100%
100%
Sort with hyphen-prefix for descending
50%
100%
Filter query parameters
100%
100%
Pagination in list response
75%
100%
Pagination links
0%
100%
ETag or Cache-Control headers
100%
100%
URL versioning present
100%
100%
Plural resource name
100%
100%
c033769
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.