api-design

Patrones de diseño REST API incluyendo nomenclatura de recursos, códigos de estado, paginación, filtrado, respuestas de error, versionado y rate limiting para APIs de producción.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Quality

Content

65%

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

The body is highly actionable with executable multi-language examples and a useful pre-publish checklist, but it is a monolithic inline reference that would benefit from progressive disclosure into separate files. Conciseness and workflow clarity are good but not exceptional given the length.

Suggestions

Move the detailed reference sections (e.g. pagination, filtering, versioning, implementation examples) into files under references/ and keep SKILL.md as a concise overview with one-level-deep links.

Add an explicit sequenced workflow for designing a new endpoint (define resource → choose methods/codes → add pagination/auth/rate-limit → run the checklist) with a validation checkpoint before publishing.

Trim inline duplication between the BIEN/MAL examples and the structured tables where one would suffice.

Dimension	Reasoning	Score
Conciseness	Per-line it is lean reference material (tables, code, conventions) with little explanation of concepts Claude already knows, but at ~500 lines the overall volume is large and much of it could be split into reference files rather than kept inline.	2 / 3
Actionability	Provides fully executable, copy-paste-ready code in TypeScript/Next.js, Python/Django, and Go, plus concrete SQL, HTTP, and JSON examples — concrete and specific throughout.	3 / 3
Workflow Clarity	Topics are clearly organized and the closing 'Lista de Verificación' acts as a validation checkpoint, but there is no explicit sequenced multi-step workflow with validation/feedback loops; it is reference material rather than a process.	2 / 3
Progressive Disclosure	Well-organized into sections, but no bundle files exist and the entire API reference lives inline in SKILL.md — hundreds of lines of reference content that could be split into separate files, matching the 'content that should be separate is inline' anchor.	2 / 3
	Total	9 / 12 Passed

Description

82%

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 specific, uses natural trigger terms, and occupies a distinct niche, but it omits any explicit 'when to use' guidance, which caps its completeness. Adding a 'Úsalo cuando...' clause would raise it to full marks.

Suggestions

Append an explicit trigger clause, e.g. 'Úsalo cuando diseñes nuevos endpoints, revises contratos de API, o agregues paginación, filtrado, errores o versionado a una API.'

Keep the existing concrete capability list — it already provides strong specificity and natural trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'nomenclatura de recursos, códigos de estado, paginación, filtrado, respuestas de error, versionado y rate limiting' — each a specific, distinct design action rather than vague language.	3 / 3
Completeness	It clearly states what the skill covers, but lacks any 'Use when...' clause or equivalent explicit trigger guidance; per the guidelines a missing explicit trigger caps completeness at 2.	2 / 3
Trigger Term Quality	Natural terms a user would say are well covered — 'REST API', 'códigos de estado', 'paginación', 'filtrado', 'versionado', 'rate limiting' — matching the vocabulary developers actually use when requesting API design help.	3 / 3
Distinctiveness Conflict Risk	Scoped tightly to 'REST API' design patterns 'para APIs de producción', a clear niche unlikely to conflict with non-API skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (524 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Commit: 4130457

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.