api-patterns

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

Quality

38%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/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 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. It reads more like a table of contents than an actionable skill description.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about choosing between REST and GraphQL, designing API endpoints, setting up pagination, or planning API versioning strategies.'

Replace topic listings with concrete action phrases, e.g., 'Guides selection between REST, GraphQL, and tRPC based on project requirements. Designs response formats, versioning strategies, and pagination patterns.'

Add file type or context triggers if applicable, e.g., 'Use 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

Implementation

29%

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 table of contents/index file, which it does well from a progressive disclosure standpoint. However, it severely lacks actionability — there are no concrete examples, decision trees, or executable guidance for API design decisions. The workflow clarity is poor because the 'Decision Checklist' is just a flat list without any actual decision-making logic or sequencing.

Suggestions

Add a concrete decision tree or flowchart for API style selection (e.g., 'If TypeScript monorepo → tRPC; If multiple client types → REST; If complex nested data needs → GraphQL') directly in the SKILL.md

Include at least one concrete, executable example — such as a minimal REST endpoint definition or a response envelope format — so the skill provides immediate value without requiring file lookups

Replace the flat decision checklist with a sequenced workflow that guides through API design steps with clear decision points and outcomes

Remove the 'When to Use' section which adds no value, and trim the 'Selective Reading Rule' which Claude already understands

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient as a hub/index file, but includes some unnecessary filler like the 'Learn to THINK, not copy fixed patterns' tagline, the 'When to Use' section that says nothing, and the selective reading rule which Claude already understands. The anti-patterns section is somewhat generic.	2 / 3
Actionability	The skill provides no concrete code, commands, or executable examples. It's entirely a table of contents pointing to other files, with a generic checklist and vague anti-patterns. The only concrete item is the script command, but there's no guidance on what it does or how to interpret results.	1 / 3
Workflow Clarity	There is no clear workflow or sequenced process for API design. The decision checklist is a flat list of yes/no questions with no guidance on what to do based on answers, no decision tree, and no validation steps. For a skill about 'decision-making,' the absence of any actual decision-making workflow is a significant gap.	1 / 3
Progressive Disclosure	The content map table is well-organized with clear file names, descriptions, and 'When to Read' guidance. References are one level deep and clearly signaled. The related skills section provides good cross-references. This is a strong hub document for navigation.	3 / 3
	Total	7 / 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: sickn33/antigravity-awesome-skills
Commit: 45d6e81

Reviewed: about 7 hours 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.