api-design

REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

A highly actionable, well-organized API design reference with strong executable examples and a useful checklist, but it is verbose in places and monolithic rather than progressively disclosed across files.

Suggestions

Move the status code reference and multi-language implementation examples into separate reference files (e.g., REFERENCE.md, EXAMPLES.md) with one-line pointers from SKILL.md to improve progressive disclosure.

Trim the HTTP method semantics table and status code catalog to only non-obvious guidance, since Claude already knows standard method/idempotency and common status code semantics.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and reference-oriented without padding, but it catalogs concepts Claude already knows (HTTP method semantics, status code tables) and runs ~500 lines that could be tightened, so it earns 2 rather than 3.	2 / 3
Actionability	It provides fully executable, copy-paste-ready examples in TypeScript/Next.js, Python/DRF, and Go, plus concrete URL, query, and SQL patterns — concrete and complete rather than pseudocode.	3 / 3
Workflow Clarity	As a reference skill it is clearly organized with a shipping checklist acting as explicit validation checkpoints and a numbered versioning strategy, satisfying the well-organized-content allowance for reference skills.	3 / 3
Progressive Disclosure	No bundle files exist and the ~500-line body is a monolithic reference whose status-code catalog and multi-language implementation examples could be split into separate files, matching the 'content that should be separate is inline' anchor at 2.	2 / 3
	Total	10 / 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.

A specific, well-scoped description with natural trigger terms and a clear niche, but it lacks an explicit 'Use when...' activation clause, capping completeness at 2.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when designing or reviewing REST APIs, adding pagination/filtering, or planning versioning strategy') to fully answer the 'when' half.

Lead with a concrete verb-first phrasing of the core action before listing sub-topics to strengthen the action orientation.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete subject areas — 'resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting' — giving a comprehensive, specific inventory rather than vague abstraction.	3 / 3
Completeness	It clearly states what the skill covers but provides no 'Use when...' clause or equivalent explicit trigger guidance, so the 'when to activate' answer is missing and completeness is capped at 2.	2 / 3
Trigger Term Quality	It uses natural terms a user would actually say ('REST API design patterns', 'status codes', 'pagination', 'error responses', 'rate limiting') with good coverage of common phrasings.	3 / 3
Distinctiveness Conflict Risk	'REST API design patterns for production APIs' carves out a clear niche with distinct triggers unlikely to overlap with unrelated 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 (525 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: affaan-m/everything-claude-code
Commit: 4130457

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