api-patterns

API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.

1.03x

Quality

60%

Does it follow best practices?

Impact

100%

1.03x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/antigravity-api-patterns/SKILL.md

Quality

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 effectively lists relevant API design topics and includes good trigger terms that developers would naturally use. However, it lacks action verbs describing what Claude does with these topics and critically omits any 'Use when...' guidance, making it unclear when this skill should be selected over others.

Suggestions

Add a 'Use when...' clause specifying triggers like 'Use when designing new APIs, choosing between REST/GraphQL/tRPC, or making decisions about API versioning and pagination strategies.'

Convert topic list into concrete actions: 'Guides API design decisions, recommends REST vs GraphQL vs tRPC based on requirements, designs pagination and versioning strategies.'

Add distinguishing context to reduce overlap: 'Use when building new APIs or refactoring existing endpoints, not for API consumption or client-side integration.'

Dimension	Reasoning	Score
Specificity	Names the domain (API design) and lists several specific topics (REST vs GraphQL vs tRPC, response formats, versioning, pagination), but these are topic areas rather than concrete actions Claude would perform.	2 / 3
Completeness	Describes what topics it covers but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no 'when' component at all.	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 guidance.	3 / 3
Distinctiveness Conflict Risk	The specific technologies (REST, GraphQL, tRPC) provide some distinctiveness, but 'API design principles' is broad enough to potentially overlap with general backend development or architecture skills.	2 / 3
	Total	8 / 12 Passed

Implementation

72%

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

This skill excels at organization and token efficiency, serving as an effective index/overview that directs users to appropriate detailed files. However, it lacks concrete examples or executable guidance in the main file itself, relying entirely on referenced documents for actionable content. The decision checklist is useful but would benefit from brief inline examples of good vs bad choices.

Suggestions

Add 1-2 brief concrete examples in the main file showing a quick decision scenario (e.g., 'Mobile app with offline needs → REST; TypeScript monorepo → tRPC')

Include a simple validation step in the decision checklist, such as 'Verified choice with user before proceeding?'

Dimension	Reasoning	Score
Conciseness	Extremely lean and efficient. Uses tables for content mapping, checklists for decisions, and bullet points for anti-patterns. No unnecessary explanations of concepts Claude already knows.	3 / 3
Actionability	Provides a decision checklist and anti-patterns which are helpful, but lacks concrete code examples or executable commands in the main file. The actionable content is deferred to referenced files rather than demonstrated here.	2 / 3
Workflow Clarity	The decision checklist provides a sequence of considerations, but there's no explicit workflow with validation checkpoints. For API design decisions, there's no feedback loop or verification step to confirm choices are appropriate.	2 / 3
Progressive Disclosure	Excellent structure with a clear content map table showing exactly when to read each file. References are one level deep, well-signaled, and organized for easy navigation. Related skills are clearly linked.	3 / 3
	Total	10 / 12 Passed

Validation

90%

Warnings & errors only

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: boisenoise/skills-collections
Commit: 5c5ae21

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.