api-patterns
Creates API route handlers, implements Server Actions with Zod schema validation, and integrates external REST APIs with error handling. Use when adding endpoints, building request handlers, or wiring external services (endpoint, REST API, request handling, fetch, .ts route files).
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%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 that clearly articulates specific capabilities (API routes, Server Actions with Zod, REST API integration), provides explicit trigger guidance via a 'Use when...' clause, and includes natural keywords users would use. It uses proper third-person voice throughout and is concise without being vague.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Creates API route handlers', 'implements Server Actions with Zod schema validation', and 'integrates external REST APIs with error handling'. These are well-defined, concrete capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (creates route handlers, implements Server Actions with Zod validation, integrates REST APIs) and 'when' with an explicit 'Use when...' clause covering adding endpoints, building request handlers, or wiring external services. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'endpoint', 'REST API', 'request handling', 'fetch', '.ts route files', 'endpoints', 'request handlers', 'external services'. Good coverage of common variations and file types. | 3 / 3 |
Distinctiveness Conflict Risk | Targets a clear niche of API route handling and server actions with specific technologies (Zod, Server Actions, .ts route files). The combination of these specific triggers makes it unlikely to conflict with general coding or frontend skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%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 skill that efficiently covers API patterns with executable code examples, clear architectural guidance, and a well-structured workflow with verification. The content respects Claude's intelligence by avoiding unnecessary explanations while providing concrete, copy-paste-ready patterns. The design rules section packs substantial guidance into concise bullet points.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It uses tables for architecture decisions, provides executable code without explaining what Next.js or Zod are, and the design rules are terse bullet points. Every section earns its place. | 3 / 3 |
Actionability | Provides fully executable TypeScript code for route handlers, server actions, and external API fetching with retry logic. Includes a concrete curl command for smoke testing and specific response/error shapes. | 3 / 3 |
Workflow Clarity | The Quick Workflow section provides a clear 5-step sequence with validation (Zod schema at step 2), testing (step 4), and a verification smoke test with a concrete curl command (step 5). The workflow covers the creation-to-verification lifecycle. | 3 / 3 |
Progressive Disclosure | The skill opens with a one-level-deep reference to project-specific config (api-config.md), then organizes content into clear sections (Architecture, Code Patterns, Quick Workflow, Design Rules). Content is appropriately scoped for a SKILL.md overview. | 3 / 3 |
Total | 12 / 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.
- Repository
- monkilabs/opencastle
- Commit
18c6f2c
- Reviewed
Table of Contents
Is this your skill?
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.