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.
Install with Tessl CLI
npx tessl i github:NeverSight/skills_feed --skill rest-patterns96
Does it follow best practices?
Validation for skill structure
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description with excellent trigger term coverage and clear 'when to use' guidance via the 'Triggers on:' clause. The main weakness is that it describes itself as a 'reference' rather than listing specific concrete actions Claude can perform, making the capabilities somewhat abstract.
Suggestions
Replace 'Quick reference for' with specific action verbs describing what the skill does, e.g., 'Guides RESTful API design, recommends HTTP methods and status codes, advises on caching strategies and rate limiting implementation.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (RESTful API design) and lists several topic areas (HTTP semantics, caching, rate limiting), but describes it as a 'quick reference' rather than listing concrete actions like 'design endpoints', 'implement rate limiting', or 'configure caching headers'. | 2 / 3 |
Completeness | Clearly answers both what ('Quick reference for RESTful API design patterns, HTTP semantics, caching, and rate limiting') and when ('Triggers on:' followed by explicit trigger terms), providing explicit guidance for skill selection. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'rest api', 'http methods', 'status codes', 'api design', 'endpoint design', 'api versioning', 'rate limiting', 'caching headers' - these are all terms developers naturally use when seeking this guidance. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on REST API design patterns with distinct triggers like 'status codes', 'api versioning', 'caching headers' that are unlikely to conflict with general coding or other API-related skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary reference skill that maximizes information density through effective use of tables, provides concrete actionable patterns, and properly delegates detailed content to referenced files. The content respects Claude's intelligence by avoiding explanations of basic concepts while providing exactly the quick-reference information needed for REST API design tasks.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Uses tables for dense information delivery, no unnecessary explanations of concepts Claude already knows (HTTP, REST basics). Every token serves a purpose. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready patterns with actual HTTP examples, specific query parameter formats, and actionable checklists. The resource design section shows exact URL patterns to use. | 3 / 3 |
Workflow Clarity | For a reference skill (not a multi-step process), the content is appropriately organized. The 'When to Use' section clarifies application contexts, and the security checklist provides clear validation steps. | 3 / 3 |
Progressive Disclosure | Excellent structure with concise overview content and clear one-level-deep references to detailed materials (status-codes.md, caching-patterns.md, etc.). Navigation is well-signaled in the Additional Resources section. | 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.