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

74%

Does it follow best practices?

Impact

94%

1.16x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./data/skills-md/0xdarkmatter/claude-mods/rest-patterns/SKILL.md

Quality

Content

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

A concise, actionable REST reference with good tables and patterns, weakened mainly by referencing four files that are not present in the bundle and by deferring caching/rate-limiting detail to those missing files.

Suggestions

Add the missing ./references/status-codes.md, caching-patterns.md, rate-limiting.md, and response-formats.md files, or remove the 'Additional Resources' section to avoid broken references.

Inline a brief Cache-Control/ETag and rate-limiting-headers example in the body so the caching and rate-limiting topics named in the description are covered even without the external files.

De-duplicate the pagination/sort/filter examples that appear in both the 'Resource Design' code block and the 'Quick Reference' table.

Dimension	Reasoning	Score
Conciseness	The body is lean: tables, a compact HTTP code block, a checklist, and a mistakes table with no padding and no explanation of concepts Claude already knows; every section earns its place.	5 / 5
Actionability	It gives concrete, copy-paste-ready HTTP method/status tables, URL patterns with real query examples, and a fix column for common mistakes; minor gaps remain because caching headers and rate-limiting headers are promised but not shown inline.	4 / 5
Workflow Clarity	As a single-purpose reference skill its single action is unambiguous and a 'When to Use' section scopes it; there is no multi-step process to sequence, and no destructive/batch operation requiring validation, so it sits just below 5 due to the absence of any explicit procedural structure.	4 / 5
Progressive Disclosure	The body is well sectioned and signals one-level-deep references ('Additional Resources' -> status-codes.md, caching-patterns.md, rate-limiting.md, response-formats.md), but none of those reference files exist in the bundle, so the advertised navigation is broken.	3 / 5
	Total	16 / 20 Passed

Description

70%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 solid, well-triggered description that clearly scopes a REST API reference skill and lists natural trigger terms. Its main weakness is action language limited to 'Quick reference for' rather than concrete capabilities.

Suggestions

Replace the generic 'Quick reference for' framing with concrete verbs, e.g. 'Look up HTTP methods, status codes, caching headers, and rate-limiting patterns when designing REST APIs.'

Add a few natural synonyms to the trigger list such as 'RESTful', 'HTTP status', and 'idempotent' to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	The description names several domains ('RESTful API design patterns, HTTP semantics, caching, and rate limiting') but the only action language is the generic phrase 'Quick reference for', with no concrete verbs like extract, generate, or validate; broad domain coverage partly compensates for the lack of concrete actions.	3 / 5
Completeness	It states both a 'what' ('Quick reference for ...') and an explicit 'when' ('Triggers on: ...' with concrete phrases), satisfying both halves; the 'what' is slightly topical rather than action-oriented, keeping it just below the top anchor.	4 / 5
Trigger Term Quality	'Triggers on: rest api, http methods, status codes, api design, endpoint design, api versioning, rate limiting, caching headers' lists natural terms a user would actually say, with good coverage, though a few common synonyms (e.g. 'RESTful', 'HTTP status') are absent.	4 / 5
Distinctiveness Conflict Risk	The REST API design niche with specific trigger terms is fairly distinct from other skills, with only minor overlap risk against broader HTTP or web-development skills.	4 / 5
	Total	15 / 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: NeverSight/skills_feed
Path: data/skills-md/0xdarkmatter/claude-mods/rest-patterns/SKILL.md
Commit: 2f57aec

Reviewed: about 22 hours 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.