api-patterns

API design principles and decision-making.

Quality

36%

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

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 critically underdeveloped and fails on all dimensions. It provides no concrete actions, lacks trigger terms users would naturally use, has no guidance on when to select this skill, and is so generic it would conflict with many other skills. Claude would struggle to know when to select this skill from a library of alternatives.

Suggestions

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

Include a 'Use when...' clause with natural trigger terms: 'Use when the user asks about REST APIs, endpoint design, API versioning, request/response formats, or OpenAPI specs'

Add file type or technology triggers to improve distinctiveness: 'swagger.yaml, openapi.json, API contracts, 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 REST endpoints', 'review API schemas', or 'generate OpenAPI specs'.	1 / 3
Completeness	The description only vaguely addresses 'what' (principles and decision-making) and completely lacks any 'when' guidance. There is no 'Use when...' clause or equivalent trigger guidance.	1 / 3
Trigger Term Quality	The only trigger term is 'API design' which is somewhat relevant but overly generic. Missing natural variations users might say like 'REST API', 'endpoints', 'API schema', 'OpenAPI', 'swagger', or 'API documentation'.	1 / 3
Distinctiveness Conflict Risk	Extremely generic and would likely conflict with any coding, architecture, or documentation skills. 'Principles and decision-making' could apply to virtually any technical domain.	1 / 3
	Total	4 / 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. However, it functions more as an index than an instructional skill - it tells Claude where to find information but provides little actionable guidance itself. The decision checklist is useful but would benefit from concrete examples or decision criteria.

Suggestions

Add a brief concrete example showing how to apply the decision checklist (e.g., 'For a mobile app with offline support → REST with caching headers')

Include at least one executable code snippet demonstrating a key pattern (e.g., a response envelope structure)

Add validation guidance to the checklist, such as 'Verify choice with user before proceeding to detailed design'

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 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 lacks explicit validation checkpoints or feedback loops. For API design decisions, there's no clear 'validate your choice' step before proceeding.	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: 3395991

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