api-patterns

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

1.03x

Quality

61%

Does it follow best practices?

Impact

98%

1.03x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

57%Weight 40%Scale 1-5

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

The body is well-structured and concise with clear navigation signaling, but actionability and workflow clarity suffer because concrete how-to detail and validation steps are deferred to reference files that are not actually present in the bundle. The missing reference files also weaken progressive disclosure despite good in-body organization.

Suggestions

Add the missing reference files (api-style.md, rest.md, response.md, graphql.md, trpc.md, versioning.md, auth.md, rate-limiting.md, documentation.md, security-testing.md) or inline the most essential decision guidance so the skill is self-contained.

Include a small executable code or configuration example in the body (e.g. a sample versioned route or pagination response envelope) rather than only deferring to reference files.

Turn the decision checklist into a sequenced workflow with explicit validation checkpoints (e.g. "validate endpoint naming against the checklist before drafting the schema").

Dimension	Reasoning	Score
Conciseness	Lean body of tables, checklists, and short DO/DON'T lists with no concept-explanation filler; minor trimmable boilerplate in the generic "When to Use"/"Limitations" sections.	4 / 5
Actionability	Provides a concrete script command and a structured decision checklist, but the bulk of how-to guidance is deferred to reference files and there are no in-body code examples, leaving it incomplete.	3 / 5
Workflow Clarity	A pre-design decision checklist gives a rough sequence but there are no validation checkpoints or feedback loops for the actual API design/build process.	3 / 5
Progressive Disclosure	In-body organization is good with a clearly signaled one-level-deep content map, but scoring against the actual bundle reveals the 10 referenced .md files do not exist, leaving the structure incomplete.	3 / 5
	Total	13 / 20 Passed

Description

66%Weight 40%Scale 1-5

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 clearly conveys a focused API-design niche with good natural trigger terms and specific sub-domains, but it lacks an explicit "when to use" clause, which limits completeness. Specificity is strong though framed as topics rather than verb-actions.

Suggestions

Add an explicit trigger clause, e.g. "Use when designing or evolving an API, choosing between REST/GraphQL/tRPC, or planning response formats, versioning, pagination, or auth."

Reframe listed items as concrete verb-actions (e.g. "Select between REST, GraphQL, and tRPC; design response formats; plan versioning and pagination") to lift specificity toward 5.

Add common synonyms users say ("endpoints", "OpenAPI/Swagger", "APIs") to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists several specific concrete sub-areas ("REST vs GraphQL vs tRPC selection, response formats, versioning, pagination"), giving comprehensive topic coverage, though they are framed as nouns rather than verb-actions.	4 / 5
Completeness	Has a clear "what" (API design principles and the listed sub-areas) but no explicit "Use when..." trigger clause, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Strong natural keywords a user would say ("API design", "REST", "GraphQL", "tRPC", "versioning", "pagination"); a few common terms like "endpoints" or "OpenAPI" are missing.	4 / 5
Distinctiveness Conflict Risk	Clear API-design niche with distinct triggers; only minor overlap risk with closely related skills like backend-development or security-hardening.	4 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/api-patterns/SKILL.md
Commit: 1f67c44

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