api-patterns

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

1.16x

Quality

61%

Does it follow best practices?

Impact

99%

1.16x

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-organized and token-efficient with a clear content map and a concrete worked example, but it is undermined by missing bundle files and the absence of explicit validation checkpoints. Delivering the referenced reference files and adding a verify step would lift the weaker dimensions.

Suggestions

Add the ten referenced .md files (api-style.md, rest.md, response.md, graphql.md, trpc.md, versioning.md, auth.md, rate-limiting.md, documentation.md, security-testing.md) to the bundle, or remove their rows from the content map to avoid broken navigation.

Insert an explicit validation/feedback checkpoint in "Inputs and procedure" (e.g. verify the proposed contract against rejection cases, then revise) to convert the sequence into a real workflow.

Move the most essential decision guidance (e.g. the REST/GraphQL/tRPC selection rule) inline so the skill remains actionable even before the reference files are read.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Claude's competence, and avoids re-explaining known concepts; minor redundancy between the decision checklist and anti-patterns sections keeps it just below 5.	4 / 5
Actionability	The worked cursor-pagination example and the validator script command are concrete, but the bulk of actionable detail is deferred to the ten referenced .md files, which are not present in the bundle, leaving key details missing.	3 / 5
Workflow Clarity	"Inputs and procedure" gives a sequenced design process and the checklist provides structure, but there is no explicit validation/feedback checkpoint (validate -> fix -> retry), so checkpoints are only implicit.	3 / 5
Progressive Disclosure	The content map is a well-signaled, one-level-deep navigation design, but ten of the eleven referenced paths (api-style.md, rest.md, response.md, etc.) do not exist in the actual bundle, so real navigation is broken rather than merely having minor gaps.	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 is specific and uses natural trigger terms within a distinct API-design niche, but it omits any explicit "Use when..." guidance, capping completeness at 3. Adding a concrete trigger clause would raise the overall score.

Suggestions

Append a "Use when..." clause naming concrete triggers (e.g. defining a new endpoint contract, choosing REST/GraphQL/tRPC, changing pagination or versioning behavior).

Consider adding auth and rate-limiting to the listed action areas so coverage reads as comprehensive rather than partial.

Dimension	Reasoning	Score
Specificity	Names the API-design domain and several concrete actions ("REST vs GraphQL vs tRPC selection, response formats, versioning, pagination"), though the opening "design principles and decision-making" is somewhat abstract, leaving minor coverage gaps (e.g. auth, rate-limiting).	4 / 5
Completeness	Clearly states what the skill does but provides no "Use when..." clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes natural terms users say (REST, GraphQL, tRPC, versioning, pagination) with good coverage, but lacks a few common synonyms or file/extension-style triggers. Not a 5 because coverage is strong rather than comprehensive.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear API-design niche with distinct triggers (REST/GraphQL/tRPC selection); minor overlap risk with closely related backend or api-security skills keeps it just below 5.	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/agentic-awesome-skills
Path: skills/api-patterns/SKILL.md
Commit: b1aebac

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