api-patterns

API design principles and decision-making.

Quality

47%

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 ./.agent/skills/api-patterns/SKILL.md

Quality

Discovery

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too brief and abstract to effectively guide skill selection. It lacks concrete actions, explicit trigger conditions, and sufficient keyword coverage. The description would benefit significantly from listing specific capabilities and adding clear 'Use when...' guidance.

Suggestions

Add specific concrete actions like 'Design RESTful endpoints, review API schemas, generate OpenAPI specifications, evaluate versioning strategies'

Include a 'Use when...' clause with explicit triggers such as 'Use when the user asks about REST APIs, endpoint design, API versioning, request/response formats, or OpenAPI specs'

Add natural keyword variations users might say: 'REST', 'endpoints', 'swagger', 'API schema', 'web services', 'HTTP methods'

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language ('principles and decision-making') without listing any concrete actions. It doesn't specify what actions Claude would take, such as 'design endpoints', 'review API schemas', or 'generate OpenAPI specs'.	1 / 3
Completeness	The description weakly addresses 'what' (API design principles) but completely lacks any 'when' guidance. There is no 'Use when...' clause or equivalent trigger guidance to help Claude know when to select this skill.	1 / 3
Trigger Term Quality	Contains 'API design' which is a relevant keyword users might say, but lacks common variations like 'REST', 'endpoints', 'OpenAPI', 'swagger', 'API schema', or 'web services' that users would naturally mention.	2 / 3
Distinctiveness Conflict Risk	'API design' provides some specificity that distinguishes it from general coding skills, but 'principles and decision-making' is vague enough that it could overlap with architecture skills, code review skills, or general software design skills.	2 / 3
	Total	6 / 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 being a concise navigation hub with excellent progressive disclosure through its content map and related skills sections. However, it functions more as an index than an instructional skill - the actual actionable guidance is entirely deferred to referenced files, and there's no concrete example of API design workflow or decision-making demonstrated in the main file itself.

Suggestions

Add one concrete, executable example showing a quick API design decision (e.g., a mini decision tree with specific code output for REST vs GraphQL choice)

Include a brief workflow sequence showing the typical API design process with validation checkpoints (e.g., 'Design → Validate with OpenAPI → Test → Document')

Add at least one copy-paste ready code snippet demonstrating a core pattern (e.g., a standard response envelope structure)

Dimension	Reasoning	Score
Conciseness	Extremely lean and efficient. Uses tables for content mapping, minimal prose, and assumes Claude understands API concepts without explanation. Every section serves a clear purpose.	3 / 3
Actionability	Provides a decision checklist and anti-patterns which are helpful, but lacks concrete code examples or executable commands. The actual 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 for multi-step API design processes, no validation checkpoints, and no feedback loops for iterating on designs.	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: Dokhacgiakhoa/antigravity-ide
Commit: 332e58b

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