product-factory/api-design
Apply this skill when designing, building, or reviewing API routes, Server Actions, or data fetching patterns in a Next.js + TypeScript + Drizzle application. Triggers on requests like "create an API endpoint", "add a server action", "design the API", "add pagination", "handle this request", "validate query params", or any time you are building the boundary between client and server. Use proactively — all API design decisions should follow these patterns.
87
Quality
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description with excellent trigger term coverage and clear completeness. The explicit 'Triggers on requests like...' clause provides concrete examples of when to activate. The main weakness is that the capabilities section could be more specific about what concrete actions the skill enables beyond the general 'designing, building, reviewing' verbs.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (API routes, Server Actions, data fetching in Next.js + TypeScript + Drizzle) and mentions some actions (designing, building, reviewing), but doesn't list specific concrete actions like 'validate input schemas', 'implement rate limiting', or 'structure response formats'. | 2 / 3 |
Completeness | Clearly answers both what (designing/building/reviewing API routes, Server Actions, data fetching patterns in Next.js stack) and when (explicit 'Triggers on requests like...' clause with multiple examples, plus 'Use proactively' guidance for boundary decisions). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'create an API endpoint', 'add a server action', 'design the API', 'add pagination', 'handle this request', 'validate query params'. These are realistic phrases developers would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically targets Next.js + TypeScript + Drizzle API patterns, client-server boundary. The technology stack combination and specific trigger terms ('server action', 'API endpoint', 'query params') make it unlikely to conflict with general coding or database skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality API design skill with excellent actionability and conciseness. The code examples are complete, typed, and production-ready. The main weaknesses are the lack of explicit workflow validation steps (e.g., 'test your endpoint with curl before proceeding') and the monolithic structure that could benefit from progressive disclosure to separate reference files.
Suggestions
Add a brief workflow section with validation checkpoints, e.g., 'After creating an endpoint: 1. Test with curl/Postman 2. Verify error responses 3. Check auth rejection'
Consider splitting pagination patterns and server action patterns into separate reference files, keeping SKILL.md as a concise overview with links
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables for quick reference, minimal prose, and letting code examples speak for themselves. No unnecessary explanations of concepts Claude already knows. | 3 / 3 |
Actionability | Every section provides fully executable TypeScript code that can be copy-pasted. Includes complete implementations for error handling, validation, pagination patterns, and server actions with proper types. | 3 / 3 |
Workflow Clarity | The decision table at the top provides good guidance on when to use what pattern, but the skill lacks explicit validation checkpoints or feedback loops for multi-step API development processes. No verification steps for testing endpoints after creation. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and headers, but it's a monolithic document (~200 lines) that could benefit from splitting detailed patterns (pagination, server actions) into separate reference files with a leaner overview. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Install with Tessl CLI
npx tessl i product-factory/api-designReviewed
Table of Contents