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.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

A well-crafted, token-efficient reference that leads with concrete examples and tables instead of concept explanations. It is actionable, clearly organized, and appropriately self-contained for its scope with no bundle files to navigate.

DimensionReasoningScore

Conciseness

The body is lean — tables and compact code blocks carry the content with no padding explaining what REST or HTTP is, assuming Claude's competence and earning every token.

3 / 3

Actionability

Concrete, copy-paste-ready guidance throughout: good/bad URL patterns, a methods table, a status-code mapping, explicit JSON response envelopes, and query-parameter syntax examples.

3 / 3

Workflow Clarity

As a conventions/reference skill with no destructive or batch operations, it is cleanly sequenced by topic (naming → methods → status codes → response format → parameters → best practices), which is unambiguous for its purpose.

3 / 3

Progressive Disclosure

The skill is short and self-contained with well-organized sections and no external bundle files, so the simple-skill allowance applies and the single-file structure is appropriate.

3 / 3

Total

12

/

12

Passed

Description

100%

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 strong, third-person description that names concrete capabilities and provides an explicit 'Use when' trigger covering several natural phrasings. It is concise, complete, and clearly niche-scoped with low conflict risk.

DimensionReasoningScore

Specificity

Explicitly enumerates four concrete capability areas — 'resource naming, HTTP methods, status codes, and response formats' — matching the anchor for listing multiple specific concrete actions rather than vague language.

3 / 3

Completeness

Clearly answers both what ('Designs RESTful APIs with proper resource naming, HTTP methods, status codes, and response formats') and when via an explicit 'Use when...' clause, satisfying the top anchor.

3 / 3

Trigger Term Quality

Natural trigger phrases a user would actually say — 'building new APIs', 'establishing API conventions', 'designing developer-friendly interfaces' — give good coverage of when this skill is needed.

3 / 3

Distinctiveness Conflict Risk

The REST API design niche with its specific triggers is clearly distinguishable from other skills and unlikely to fire for the wrong skill.

3 / 3

Total

12

/

12

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.