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

91%

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

82%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.

The body is a concise, highly actionable API-patterns reference with exact shapes, status codes, and a verification command, organized into clear sections. Its main gaps are the absence of a complete executable handler example and a broken external reference.

Suggestions

Add one complete, copy-paste-ready route.ts (or Server Action) example that demonstrates the Zod validation, envelope, and error shape together to lift actionability to fully executable.

Fix or remove the api-config.md reference — the path ../../.opencastle/stack/api-config.md does not exist, so the link is dead; either point it at a real file or inline the config note.

Make the handler workflow explicit as a short numbered sequence (validate → authorize → act → respond) with the curl smoke-test as the final verification step to reach the explicit-checklist anchor.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it never explains what REST, Zod, or Server Actions are, and every line (architecture table, rules list, smoke-test command) earns its place, matching the lean/efficient anchor.	5 / 5
Actionability	Guidance is highly concrete with exact JSON envelope/error shapes, status code set, retry backoff ('500 ms × attempt'), pagination params, and a copy-paste curl smoke-test, but it stops short of a full executable route.ts handler example, leaving it just below the fully copy-paste-ready bar.	4 / 5
Workflow Clarity	A clear sequence is implied (validate input with Zod at the top → handle → return envelope/error) and an explicit verification checkpoint exists (the curl smoke-test), but it is a rules reference rather than an enumerated multi-step workflow, so it sits at clear-sequence-with-minor-gaps rather than the explicit-checklist anchor.	4 / 5
Progressive Disclosure	Content is well organized into Architecture and Rules sections with a clearly signaled one-level reference to api-config.md, but that referenced path does not exist in the bundle, which prevents a clean 5 for navigation.	4 / 5
	Total	17 / 20 Passed

Description

100%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.

The description is a strong, third-person statement that concisely captures what the skill does and when to use it, with concrete actions, natural trigger terms, and a file extension. It matches the top anchor on every dimension with no verbosity or over-claims.

Dimension	Reasoning	Score
Specificity	Lists three concrete actions with specific technology — 'Creates API route handlers, implements Server Actions with Zod schema validation, integrates external REST APIs with error handling' — which is comprehensive coverage rather than the 1-2 actions of a score-3 anchor.	5 / 5
Completeness	Explicitly answers both 'what' (route handlers, Server Actions, REST integration) and 'when' ('Use when adding endpoints, building request handlers, or wiring external services') with concrete trigger phrases, matching the score-5 anchor.	5 / 5
Trigger Term Quality	Covers natural synonyms and a file extension — 'endpoint, REST API, request handling, fetch, .ts route files' alongside 'adding endpoints, building request handlers, or wiring external services' — matching the comprehensive coverage anchor.	5 / 5
Distinctiveness Conflict Risk	The Server Actions / route.ts / Zod-validation niche has distinct triggers and minimal overlap with unrelated skills; voice is correctly third person ('Creates', 'implements', 'integrates').	5 / 5
	Total	20 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

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

Reviewed: 5 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.