api-designer
Use when designing REST or GraphQL APIs, creating OpenAPI specifications, or planning API architecture. Invoke for resource modeling, versioning strategies, pagination patterns, error handling standards.
99
100%
Does it follow best practices?
Impact
98%
1.00xAverage score across 6 eval scenarios
Passed
No known issues
Quality
Discovery
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.
This is a well-crafted skill description that excels across all dimensions. It provides specific concrete actions, uses natural developer terminology as trigger terms, explicitly states both what the skill does and when to use it, and carves out a distinct niche in API design that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'designing REST or GraphQL APIs', 'creating OpenAPI specifications', 'planning API architecture', 'resource modeling', 'versioning strategies', 'pagination patterns', 'error handling standards'. | 3 / 3 |
Completeness | Clearly answers both what (designing APIs, creating specs, planning architecture, various patterns) and when with explicit 'Use when' and 'Invoke for' clauses that specify trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'REST', 'GraphQL', 'APIs', 'OpenAPI specifications', 'API architecture', 'resource modeling', 'versioning', 'pagination', 'error handling' - all common developer vocabulary. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on API design with distinct triggers like 'REST', 'GraphQL', 'OpenAPI', 'pagination patterns' that are unlikely to conflict with general coding or documentation skills. | 3 / 3 |
Total | 12 / 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 skill file that demonstrates best practices across all dimensions. It provides comprehensive, actionable guidance with executable templates, clear workflow with validation checkpoints, and well-organized progressive disclosure through the reference table. The MUST DO/MUST NOT DO constraints are specific and bounded without being verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, avoiding explanations of concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context about what APIs are or how REST works. | 3 / 3 |
Actionability | Provides fully executable OpenAPI 3.1 YAML template that is copy-paste ready, concrete CLI commands for validation and mocking, and specific RFC 7807 error response examples. All guidance is immediately actionable. | 3 / 3 |
Workflow Clarity | Clear 6-step workflow with explicit validation checkpoint (step 4: lint before proceeding) and verification step (step 5: mock server testing). The output checklist reinforces validation with 'passes with no errors' requirement. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, reference table pointing to one-level-deep topic files (rest-patterns.md, versioning.md, etc.), and clear 'Load When' guidance. Templates are appropriately inline as they're core to the 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jeffallan/claude-skills
- Commit
5b76101
- 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.