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

85%

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.

An exemplary lean, project-specific pattern reference: dense actionable rules with exact response/error shapes and a concrete smoke-test command, well-organized into short sections. The only meaningful gap is the absence of a complete executable handler example to anchor the rules.

Suggestions

Add a minimal copy-paste-ready route.ts or Server Action example showing the Zod validation, response envelope, and error shape together so the rules are directly executable.

Optionally number the workflow (choose layer -> validate input -> shape response -> smoke-test) so the implicit sequence and the curl verification become an explicit feedback loop.

Dimension	Reasoning	Score
Conciseness	The ~25-line body contains no explanation of concepts Claude already knows; every line carries project-specific rules (envelope shape, error shape, status codes, retry policy, paths). This matches anchor 5 — lean, efficient, every token earns its place.	5 / 5
Actionability	Guidance is highly concrete — exact JSON envelope and error shapes, an explicit status-code set, retry parameters ("twice with linear backoff (500 ms × attempt)"), and a runnable curl smoke-test command. It stops short of anchor 5 because there is no copy-paste-ready handler code skeleton (e.g. a minimal route.ts or Server Action with Zod) covering the common case.	4 / 5
Workflow Clarity	The rules imply a clear order (choose layer, validate with Zod, shape response, smoke-test) and the curl smoke-test is an explicit verification checkpoint, matching anchor 4. It is not anchor 5 because the steps are not explicitly sequenced with feedback loops for error recovery; it is above anchor 3 because a concrete validation step exists.	4 / 5
Progressive Disclosure	The skill is under 50 lines, needs no external reference files, and is organized into clear sections (Architecture table, Rules, smoke test). Per the rubric's guideline for short skills, this matches anchor 5; the one external pointer (.opencastle/stack/api-config.md) is a clearly signaled project-config path, one level deep.	5 / 5
	Total	18 / 20 Passed

Description

83%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 description with three concrete capabilities, an explicit 'Use when...' clause, and a useful parenthetical keyword list. It is held back from top marks only by minor coverage and keyword gaps.

Suggestions

Add 'server actions' and 'API' to the trigger keyword list so users phrasing requests around those exact terms match naturally.

Consider mentioning the proxy/rate-limiting layer (e.g. 'adds a proxy layer for IP rate limiting and bot detection') so the description covers the full capability scope described in the body.

Dimension	Reasoning	Score
Specificity	"Creates API route handlers, implements Server Actions with Zod schema validation, integrates external REST APIs with error handling" lists several specific concrete actions with technical detail. It falls short of anchor 5 (comprehensive coverage) because the skill's proxy-layer/rate-limiting capability is not surfaced, and exceeds anchor 3 because more than 1-2 actions are named.	4 / 5
Completeness	"Creates API route handlers, implements Server Actions... integrates external REST APIs" explicitly states what the skill does, and "Use when adding endpoints, building request handlers, or wiring external services" gives an explicit when with concrete trigger phrases — a direct match for anchor 5.	5 / 5
Trigger Term Quality	The trigger list "(endpoint, REST API, request handling, fetch, .ts route files)" gives good natural keyword coverage including a file extension. A few natural terms users would say are missing (e.g. "server action", "API" as a standalone trigger), keeping it at anchor 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	The niche (route handlers, Server Actions with Zod, external REST integration) is clear and the triggers are specific, but there is minor overlap risk with generic backend/API-service skills, matching anchor 4 rather than the minimal-conflict profile of anchor 5.	4 / 5
	Total	17 / 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: c0f4566

Reviewed: 1 day 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.