api-patterns
API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.
57
37%
Does it follow best practices?
Impact
92%
1.14xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/antigravity-awesome-skills-claude/skills/api-patterns/SKILL.mdQuality
Discovery
47%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description provides good keyword coverage for API design topics and names specific technologies, which aids discoverability. However, it lacks action verbs describing what the skill concretely does and entirely omits a 'Use when...' clause, making it unclear when Claude should select this skill over others. Converting the topic list into concrete actions and adding explicit trigger conditions would significantly improve it.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user asks about designing APIs, choosing between REST/GraphQL/tRPC, or needs guidance on API versioning, pagination, or response format decisions.'
Replace topic labels with action-oriented descriptions, e.g., 'Guides API design decisions including selecting between REST, GraphQL, and tRPC, structuring response formats, implementing versioning strategies, and designing pagination patterns.'
Consider adding more natural trigger terms like 'endpoint design', 'API architecture', 'HTTP API', or 'API best practices' to capture common user phrasings.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (API design) and lists some specific topics like REST vs GraphQL vs tRPC selection, response formats, versioning, and pagination, but these read more like topic labels than concrete actions (no verbs describing what the skill does). | 2 / 3 |
Completeness | Describes 'what' at a topic level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also weak (topics rather than actions), warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'API design', 'REST', 'GraphQL', 'tRPC', 'versioning', 'pagination', 'response formats'. These are terms developers naturally use when seeking API design guidance. | 3 / 3 |
Distinctiveness Conflict Risk | The mention of specific technologies (REST, GraphQL, tRPC) and specific concerns (versioning, pagination) provides some distinctiveness, but 'API design principles and decision-making' is broad enough to potentially overlap with general architecture or backend development skills. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a table of contents with no substantive content in the body itself. It references 10 supporting files and 3 related skills, none of which are provided in the bundle, making the skill non-functional. The body lacks any concrete, executable guidance—no code examples, no specific API design patterns, no decision trees—just checklists and pointers to absent resources.
Suggestions
Include at least a concise decision tree or flowchart inline (e.g., REST vs GraphQL vs tRPC selection criteria with concrete examples) so the skill is useful even without bundle files.
Add at least one concrete, executable code example—such as a sample REST endpoint definition, response envelope format, or OpenAPI snippet—to make the skill actionable on its own.
Provide the referenced bundle files (api-style.md, rest.md, response.md, etc.) or consolidate the most critical content inline so the skill isn't an empty shell.
Remove the generic boilerplate sections ('When to Use', 'Limitations') and the motivational tagline to improve conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content map and checklist are efficient, but the boilerplate sections at the bottom ('When to Use', 'Limitations') add generic filler that Claude doesn't need. The tagline 'Learn to THINK, not copy fixed patterns' is unnecessary fluff. The anti-patterns section is somewhat generic and could be tighter. | 2 / 3 |
Actionability | The skill body contains no executable code, no concrete API examples, no specific commands beyond a script invocation, and no actual design guidance—it's entirely a table of contents and checklists pointing to other files. The anti-patterns are vague platitudes ('Choose API style based on context') rather than concrete, actionable instructions. | 1 / 3 |
Workflow Clarity | The decision checklist provides a reasonable sequence of considerations before designing an API, but there are no validation checkpoints, no feedback loops, and no clear step-by-step workflow for actually executing an API design task. The checklist is more of a reminder list than a guided workflow. | 2 / 3 |
Progressive Disclosure | The content map references 10 separate files (api-style.md, rest.md, response.md, etc.) and 3 related skills, but NO bundle files were provided, meaning all referenced content is missing. The SKILL.md itself is essentially an empty shell—nearly all substantive content is deferred to non-existent files, making the skill non-functional in isolation. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
a4d3e3a
- 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.