CtrlK
BlogDocsLog inGet started
Tessl Logo

rest-api-design

Designs RESTful APIs with proper resource naming, HTTP methods, status codes, and response formats. Use when building new APIs, establishing API conventions, or designing developer-friendly interfaces.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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.

A tight, well-structured REST API reference that maximizes token efficiency and gives concrete examples across all key areas. It is held just below the top band because it is reference material without a guided workflow or progressive file structure.

Suggestions

Add a short ordering/workflow note (e.g., 'name resources → choose methods → assign status codes → shape responses') to turn the reference into an unambiguous design sequence.

For destructive or batch-style API changes, include a brief validation checkpoint (e.g., confirm idempotency and correct status code before finalizing a route design) to lift workflow clarity.

If the conventions grow, move the status-code and response-format tables into a linked reference file to keep SKILL.md a lean overview and support progressive disclosure.

DimensionReasoningScore

Conciseness

The body is lean — compact tables and short code/JSON blocks with no padding or explanation of concepts Claude already knows — so every token earns its place, matching the top anchor.

5 / 5

Actionability

It provides concrete, copy-paste-ready patterns (real routes, status code tables, JSON envelopes, query-param examples), but as a reference/cheat-sheet it lacks executable commands or end-to-end runnable code, keeping it just below level 5.

4 / 5

Workflow Clarity

There is no multi-step workflow, but as a single-purpose conventions skill the action is reasonably unambiguous and the sections are well-ordered; it stops short of 5 because no validation/checklist sequence is presented for applying the conventions.

4 / 5

Progressive Disclosure

Content is organized into clear, well-labeled sections (Resource Naming, HTTP Methods, Status Codes, Response Format, etc.) with no unnecessary nesting; it stays at 4 rather than 5 because the body is self-contained with no signaled one-level-deep references and runs slightly long for a single file.

4 / 5

Total

17

/

20

Passed

Description

83%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 well-crafted description that is specific, uses third-person voice, and clearly states both capability and trigger conditions. It sits just below the top tier due to a couple of slightly broad trigger phrases and minor synonym gaps.

DimensionReasoningScore

Specificity

The description lists several concrete capability areas — 'resource naming, HTTP methods, status codes, and response formats' — giving good coverage with only minor gaps, matching the 'several specific actions' anchor rather than the fully comprehensive level 5.

4 / 5

Completeness

It explicitly answers both 'what' ('Designs RESTful APIs with proper resource naming, HTTP methods, status codes, and response formats') and 'when' via a concrete 'Use when ...' clause with multiple trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

It includes natural user phrases such as 'building new APIs', 'establishing API conventions', and 'designing developer-friendly interfaces', providing good keyword coverage, though a few common synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

The 'RESTful APIs' niche is mostly distinct with clear triggers, though the broad phrase 'designing developer-friendly interfaces' carries minor overlap risk with general design skills.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
secondsky/claude-skills
Reviewed

Table of Contents

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.