api-endpoint-builder

Builds production-ready REST API endpoints with validation, error handling, authentication, and documentation. Follows best practices for security and scalability.

Quality

66%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/api-endpoint-builder/SKILL.md

Quality

Content

65%

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

The skill is highly actionable with complete, executable code examples, but it is padded with reference material Claude already knows and keeps all content inline rather than using progressive disclosure. Workflow sequencing is present but lacks explicit validation checkpoints.

Suggestions

Move the HTTP status-code reference, full pagination/filtering patterns, and documentation/testing templates into reference files (e.g., REFERENCE.md, TESTING.md) and link to them from the overview.

Remove the 'Key Principles' section and security checklist content that restates knowledge Claude already has; keep only skill-specific guidance.

Add an explicit build workflow with validation checkpoints (e.g., validate input -> run handler -> verify response shape -> add tests) so the sequence has a feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete code, but the HTTP status-code list, security checklist, and 'Key Principles' restate concepts Claude already knows and could be trimmed.	2 / 3
Actionability	Provides fully executable Express/Fastify route definitions, validateUser, createUser, pagination, filtering, documentation, and test code that is copy-paste ready.	3 / 3
Workflow Clarity	The endpoint structure is sequenced (route -> validate -> handle), but there are no explicit validation checkpoints or feedback loops tying testing back into the build flow.	2 / 3
Progressive Disclosure	Sections are well-organized, but everything is inline in a single ~320-line SKILL.md with no references or split files, so content that could be separate stays monolithic.	2 / 3
	Total	9 / 12 Passed

Description

67%

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 distinct, naming concrete capabilities in proper third-person voice, but lacks an explicit 'Use when...' trigger clause and has thin trigger-term coverage. It is strong on what and weak on when.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g., 'Use when the user asks to create an API endpoint, build a REST API, or add a route').

Broaden trigger terms to include common variations users say: 'API', 'endpoint', 'route', 'CRUD', and 'backend'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'validation, error handling, authentication, and documentation' — matching the anchor for naming several specific capabilities rather than vague language.	3 / 3
Completeness	It clearly states what the skill does but omits any 'Use when...' clause or explicit trigger guidance, which the rubric caps at 2.	2 / 3
Trigger Term Quality	Only 'REST API endpoints' appears as a natural trigger; common variations users would say (route, API, CRUD, backend) are missing, so it stops short of full coverage.	2 / 3
Distinctiveness Conflict Risk	'Builds production-ready REST API endpoints' is a clear, narrow niche with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 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
Commit: 6b7501e

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