Install any skill in seconds. Free to start, no credit card required.
Get Started Free →xu-xiang/api-design
生产级 API 的 REST API 设计模式,包括资源命名、状态码、分页、过滤、错误响应、版本控制和速率限制。
Passed 22 of 23 test cases with the skill, and 16 of 23 without it.
and 7 more in the full report
6 fixed16 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am building a web backend for managing customer shipping addresses and order history in our microservices system. Please design the OpenAPI-style REST API specification for these resources. Include endpoint paths, HTTP verbs, standard request/response payloads for single items and paginated collections, and an error structure for input validation failures. Present the final design as a structured Markdown document with code snippets for payload examples.
| Checked | Without skill | With skill |
|---|---|---|
| Error responses wrap error details under a top-level error key. | Missed | Passed |
| Paginated collection metadata is structured inside a meta object. | Missed | Passed |
| Collection pagination uses snake_case keys like per_page or total_pages. | Missed | Passed |
The instructions your model reads when the skill loads.
用于设计一致、对开发者友好的 REST API 的约定和最佳实践。
# Resources are nouns, plural, lowercase, kebab-case
GET /api/v1/users
GET /api/v1/users/:id
POST /api/v1/users
PUT /api/v1/users/:id
PATCH /api/v1/users/:id
DELETE /api/v1/users/:id
# Sub-resources for relationships
GET /api/v1/users/:id/orders
POST /api/v1/users/:id/orders
# Actions that don't map to CRUD (use verbs sparingly)
POST /api/v1/orders/:id/cancel
POST /api/v1/auth/login
POST /api/v1/auth/refresh
# GOOD
test cases passed, vs 16 / 23 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.