api-patterns

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

1.14x

Quality

44%

Does it follow best practices?

Impact

92%

1.14x

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 provides decent keyword coverage for API design topics but lacks action-oriented language and an explicit 'Use when...' clause. It reads more like a table of contents than a functional skill description, making it harder for Claude to know precisely when to select it over other skills.

Suggestions

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

Rewrite with concrete action verbs: 'Guides API design decisions including selecting between REST, GraphQL, and tRPC, designing response formats, implementing versioning strategies, and configuring pagination patterns.'

Add additional trigger terms users might say, such as 'endpoint design', 'API architecture', 'HTTP API', or 'API best practices'.

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 as 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 API-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

Implementation

42%

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

This skill functions primarily as a well-organized index/table of contents for sub-files, with good progressive disclosure and navigation. However, the main body itself lacks any concrete, actionable content — no code examples, no executable commands, no specific API design patterns. The anti-patterns and checklist sections are too generic and don't add much value beyond what Claude already knows.

Suggestions

Add at least one concrete, executable example in the main file — e.g., a sample REST endpoint definition, a response envelope JSON schema, or a quick decision tree with specific code snippets for each API style.

Replace the generic anti-patterns section with specific, non-obvious guidance or common mistakes with concrete before/after examples.

Remove the boilerplate 'When to Use' and 'Limitations' sections which add no actionable information and waste tokens.

Add a brief workflow with validation steps for the API design process, e.g., 'Design → Validate with api_validator.py → Review output → Iterate', with expected output examples from the validator script.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with a clean table-based content map, but includes some filler like the motivational tagline 'Learn to THINK, not copy fixed patterns', the generic 'When to Use' and 'Limitations' boilerplate sections, and the anti-patterns section which largely states things Claude already knows (e.g., don't use verbs in REST endpoints).	2 / 3
Actionability	The skill body contains no concrete code, commands, examples, or executable guidance. It's essentially a table of contents pointing to other files, a checklist of questions, and a list of do's/don'ts — all abstract direction with no specific, actionable content. The script reference is the only concrete element but lacks usage examples or expected output.	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 API design tasks. The checklist is more of a reminder list than a guided workflow.	2 / 3
Progressive Disclosure	The content map table is well-structured with clear file names, descriptions, and 'When to Read' guidance. References are one level deep, clearly signaled, and the selective reading rule is explicit. Related skills are also well-linked.	3 / 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: 431bfad

Reviewed: 2 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.