api-patterns

Creates API route handlers, implements Server Actions with Zod schema validation, 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).

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, well-structured API patterns reference that assumes Claude's competence and gives concrete, actionable rules plus a verification smoke-test. The main gap is the absence of a complete route-handler code example to anchor the patterns.

Suggestions

Add one short, copy-paste route-handler example showing Zod validation, the response envelope, and the error shape applied end-to-end.

Turn the closing smoke-test into an explicit validate-then-fix feedback loop (e.g., 'If curl fails with 4xx, check Zod schema and error code mapping; re-run until 2xx').

Clarify where the proxy-layer rate limiting is configured (file/path) so the rule is directly actionable rather than descriptive.

Dimension	Reasoning	Score
Conciseness	The body is lean: a compact architecture table, terse rule bullets, exact JSON shapes, and one smoke-test command, with no padding or explanation of concepts Claude already knows, matching the lean/every-token-earns-its-place anchor.	5 / 5
Actionability	Guidance is mostly executable — concrete response/error JSON envelopes, status codes, versioned URL pattern, retry formula '500 ms × attempt', and a copy-paste curl command — but it stops short of a full copy-paste route-handler code example, leaving a minor gap versus the fully-executable anchor.	4 / 5
Workflow Clarity	The rules form a clear checklist and the closing curl smoke-test is an explicit validation checkpoint, but the body is a rule reference rather than a strictly sequenced multi-step workflow, so it sits at clear-sequence-with-minor-gaps rather than the explicit-feedback-loop anchor.	4 / 5
Progressive Disclosure	Under 50 lines and well-organized into Architecture and Rules sections, with a single clearly-signaled one-level-deep reference ('.opencastle/stack/api-config.md'); per the simple-skill note, this satisfies the clear-overview anchor without needing bundle files.	5 / 5
	Total	18 / 20 Passed

Description

91%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that concretely states capabilities and provides an explicit, keyword-rich 'Use when' trigger clause with synonyms and a file extension. The only soft spot is a slight overlap risk on generic fetch/integration triggers.

Dimension	Reasoning	Score
Specificity	Lists three concrete actions ('Creates API route handlers', 'implements Server Actions with Zod schema validation', 'integrates external REST APIs with error handling'), matching the anchor for several specific actions with minor coverage gaps rather than the comprehensive multi-action anchor at 5.	4 / 5
Completeness	It explicitly answers 'what' (the three creation/integration actions) and 'when' via a concrete 'Use when adding endpoints, building request handlers, or wiring external services' clause, satisfying the top anchor.	5 / 5
Trigger Term Quality	The parenthetical '(endpoint, REST API, request handling, fetch, .ts route files)' plus 'adding endpoints, building request handlers, wiring external services' covers natural terms, synonyms (endpoint/endpoints, request handling/handlers), and a file extension, matching the comprehensive-coverage anchor.	5 / 5
Distinctiveness Conflict Risk	The niche (Server Actions, route handlers, REST integration with .ts route files) is mostly distinct with a clear trigger set, though 'fetch' and 'external services' carry minor overlap risk with generic integration skills rather than the minimal-conflict anchor at 5.	4 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: monkilabs/opencastle
Path: src/orchestrator/skills/api-patterns/SKILL.md
Commit: f297837

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.