rest-patterns

Quick reference for RESTful API design patterns, HTTP semantics, caching, and rate limiting. Triggers on: rest api, http methods, status codes, api design, endpoint design, api versioning, rate limiting, caching headers.

1.16x

Quality

—

Does it follow best practices?

Impact

94%

1.16x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

92%

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

A clean, token-efficient reference skill with concrete examples and good organization. The sole defect is progressive disclosure: the body advertises four reference files that are not present in the bundle.

Suggestions

Create the referenced bundle files under ./references/ (status-codes.md, caching-patterns.md, rate-limiting.md, response-formats.md) so the "Additional Resources" links resolve.

Alternatively, remove the "Additional Resources" section or mark the references as optional/to-be-created so the skill does not point to missing files.

Dimension	Reasoning	Score
Conciseness	The body is lean tables and short code blocks with no padded explanation of concepts Claude already knows; every section earns its place.	3 / 3
Actionability	It provides concrete, copy-paste-ready patterns (e.g. "GET /users?page=2&limit=20"), specific status-code/method tables, and an actionable security checklist.	3 / 3
Workflow Clarity	As a single-purpose lookup skill with no destructive multi-step process, its clearly organized sections (methods, status codes, common mistakes) satisfy the simple-skill allowance for a top score.	3 / 3
Progressive Disclosure	The "Additional Resources" section clearly signals one-level-deep references, but the listed files (./references/status-codes.md, caching-patterns.md, rate-limiting.md, response-formats.md) do not exist, so navigation is broken.	2 / 3
	Total	11 / 12 Passed

Description

90%

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 well-constructed description with explicit trigger guidance and a clear, distinctive niche. Its only soft spot is specificity, which lists topic areas rather than concrete verb-driven actions.

Dimension	Reasoning	Score
Specificity	It names the REST API domain plus several concrete sub-areas ("HTTP semantics, caching, and rate limiting"), but frames them as topics rather than a list of specific concrete actions with verbs, so it sits below the 3 anchor.	2 / 3
Completeness	It answers both "what" (quick reference for RESTful API design patterns, HTTP semantics, caching, rate limiting) and "when" via the explicit "Triggers on:" clause.	3 / 3
Trigger Term Quality	"Triggers on: rest api, http methods, status codes, api design, endpoint design, api versioning, rate limiting, caching headers" gives good coverage of natural terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	It occupies a clear niche (REST API design) with distinct, specific triggers unlikely to collide with other skills.	3 / 3
	Total	11 / 12 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: NeverSight/skills_feed
Commit: 26d37ce

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.