Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.
62
44%
Does it follow best practices?
Impact
91%
1.03xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/02-architect-apidesign/SKILL.mdREST resource-oriented design and pagination
Plural collection names
100%
100%
No action-based endpoints
100%
100%
Correct HTTP method usage
100%
100%
Nested resource endpoints
100%
100%
Pagination query parameters
100%
100%
Paginated response shape
100%
100%
HATEOAS _links
75%
100%
Consistent error response structure
70%
100%
Correct status codes
100%
100%
API versioning present
0%
0%
Filtering support
100%
100%
GraphQL schema design with Relay pagination and DataLoaders
Relay cursor pagination
100%
100%
PageInfo fields
100%
100%
totalCount on Connection
100%
100%
Mutation Input types
100%
100%
Mutation Payload types
100%
100%
Structured mutation errors
100%
100%
DataLoader for N+1
83%
100%
Enums for status fields
0%
0%
Custom scalars
100%
100%
@deprecated directive
0%
0%
Schema defined before resolvers
100%
100%
REST error handling, HATEOAS, and API versioning
No POST-for-everything
100%
100%
Plural collection endpoint
100%
100%
Correct error status codes
100%
100%
Structured error response
100%
100%
HATEOAS _links in responses
80%
100%
API versioning in paths
100%
100%
OpenAPI spec produced
100%
100%
Rate limiting mentioned
100%
100%
Not tight-coupled to DB schema
100%
100%
Versioning migration path documented
100%
100%
3dd3ac0
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.