API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.
74
61%
Does it follow best practices?
Impact
99%
1.16xAverage score across 3 eval scenarios
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/api-patterns/SKILL.mdAPI technology selection: tRPC vs GraphQL vs REST
tRPC for Project A
0%
100%
Project A reasoning
0%
100%
tRPC runtime validation
0%
100%
GraphQL for Project B
100%
100%
Project B reasoning
100%
100%
GraphQL depth protection
100%
100%
GraphQL complexity protection
100%
100%
GraphQL batch protection
100%
100%
Introspection as policy choice
100%
100%
GraphQL schema evolution
100%
100%
REST API design with OpenAPI spec for task management service
Noun-based paths
70%
100%
Plural resource forms
100%
100%
Path depth within limit
100%
100%
201 for resource creation
100%
100%
204 for deletions
100%
100%
422 for validation errors
50%
100%
Consistent response format
100%
100%
Error code field
100%
100%
Request ID in errors
100%
100%
No internal error details exposed
100%
100%
Cursor or keyset pagination
100%
100%
Rate limiting in OpenAPI
60%
100%
Validator script run
100%
100%
Auth and rate limiting spec for a public weather API
API Key auth
100%
100%
OAuth 2.0 for users
100%
100%
JWT single algorithm
100%
70%
JWT issuer and audience
100%
100%
JWT short expiry + refresh
100%
100%
JWT no sensitive data
100%
100%
Token bucket algorithm
100%
100%
X-RateLimit-Limit header
100%
100%
X-RateLimit-Remaining header
100%
100%
X-RateLimit-Reset header
100%
100%
HTTP 429 status code
100%
100%
requestId in errors
100%
100%
No internal error details
100%
100%
URI versioning
100%
100%
b1aebac
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.