api-patterns

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

1.14x

Quality

37%

Does it follow best practices?

Impact

92%

1.14x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/antigravity-api-patterns/SKILL.md

Quality

Content

27%

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

This skill functions as a table of contents / navigation hub that delegates all substantive content to referenced files, none of which are provided in the bundle. The main file itself contains no executable code, no concrete API design guidance, and no real workflow beyond a checklist. While the organizational structure (content map, anti-patterns, checklist) shows good intent, the absence of any actionable content in the body or supporting files makes this skill largely non-functional.

Suggestions

Include at least the core referenced files (api-style.md, rest.md, response.md) in the bundle so the progressive disclosure structure actually works, or inline the most critical decision-making content directly in SKILL.md.

Add a concrete, executable quick-start example — e.g., a sample REST endpoint definition with proper naming, status codes, and response envelope format — so the skill provides immediate actionable value.

Replace the vague anti-patterns ('Default to REST for everything') with specific decision criteria, such as 'Use GraphQL when clients need to fetch nested resources with varying shapes; use REST when you have simple CRUD with well-defined resources.'

Remove the generic 'When to Use' and 'Limitations' boilerplate sections that add no skill-specific value and waste tokens.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with a clean table-based content map, but includes some unnecessary filler like the 'When to Use' and 'Limitations' boilerplate sections that add little value, and the motivational tagline 'Learn to THINK, not copy fixed patterns' is padding.	2 / 3
Actionability	The skill body contains no concrete code, commands (beyond a script invocation), executable examples, or specific API design guidance. It is entirely a navigation hub with checklists and anti-pattern lists that are vague ('Choose API style based on context') rather than instructive. The actual actionable content is deferred entirely to referenced files that are not provided.	1 / 3
Workflow Clarity	The decision checklist provides a reasonable sequence of considerations before designing an API, but there are no validation checkpoints, feedback loops, or 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 related skills, but none of the bundle files are provided, making it impossible to verify they exist or contain useful content. The SKILL.md itself is essentially hollow — it delegates everything to files that don't appear to exist, making the progressive disclosure structure non-functional.	1 / 3
	Total	6 / 12 Passed

Description

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 concrete capabilities 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 guidance would significantly improve it.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user asks about choosing between REST, GraphQL, or tRPC, designing API endpoints, structuring API responses, or implementing pagination or versioning strategies.'

Replace topic nouns with concrete action phrases, e.g., 'Guides selection between REST, GraphQL, and tRPC architectures. Designs response formats, versioning strategies, and pagination schemes.'

Add file type or context triggers if applicable, e.g., 'when reviewing OpenAPI specs, designing new endpoints, or planning API architecture.'

Dimension	Reasoning	Score
Specificity	Names the domain (API design) and lists several specific topics (REST vs GraphQL vs tRPC selection, response formats, versioning, pagination), but these read more like topic areas than concrete actions. No action verbs like 'design', 'evaluate', or 'implement' are used.	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' is broad enough to potentially overlap with general backend development or architecture skills.	2 / 3
	Total	8 / 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: c45b103

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.