api-endpoint-builder

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

Quality

37%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/antigravity-awesome-skills-claude/skills/api-endpoint-builder/SKILL.md

Quality

Discovery

32%

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 identifies a clear domain (REST APIs) and lists relevant concerns but remains at a category level rather than specifying concrete actions. The biggest weakness is the complete absence of a 'Use when...' clause, which is critical for skill selection. The trailing sentence about 'best practices for security and scalability' is vague filler that adds little discriminative value.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'Use when the user asks to create an API, build REST endpoints, set up routes, or scaffold a backend server.'

Replace the vague 'Follows best practices for security and scalability' with concrete actions such as 'generates OpenAPI/Swagger docs, implements rate limiting, adds JWT or OAuth middleware.'

Include common user-facing keywords and variations such as 'HTTP routes', 'CRUD operations', 'API server', 'Express', 'FastAPI', or 'backend endpoints' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (REST API endpoints) and lists some actions/concerns (validation, error handling, authentication, documentation), but these read more like feature categories than concrete actions. It doesn't specify formats, frameworks, or granular operations like 'define route handlers, generate OpenAPI specs, implement JWT auth middleware.'	2 / 3
Completeness	The description answers 'what' (builds REST API endpoints with various features) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'when' is entirely absent and the 'what' is also somewhat vague, this scores at the lower end.	1 / 3
Trigger Term Quality	Includes relevant terms like 'REST API', 'endpoints', 'authentication', 'validation' that users might naturally say, but misses common variations such as 'HTTP routes', 'API server', 'CRUD', 'middleware', 'Express', 'FastAPI', or file extensions. Coverage is partial.	2 / 3
Distinctiveness Conflict Risk	The focus on REST API endpoints provides some specificity, but terms like 'validation', 'error handling', 'authentication', and 'documentation' are broad enough to overlap with general backend development skills, web framework skills, or security-focused skills.	2 / 3
	Total	7 / 12 Passed

Implementation

42%

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

This skill provides highly actionable, executable code examples for building REST API endpoints, which is its primary strength. However, it is severely over-verbose, explaining many concepts Claude already knows (HTTP status codes, CRUD patterns, basic middleware), and dumps everything into a single monolithic file with no progressive disclosure. The workflow is more of a pattern catalog than a sequenced process with validation checkpoints.

Suggestions

Cut the HTTP status codes list, security checklist, and 'Key Principles' section entirely — Claude already knows these. Focus only on project-specific conventions or non-obvious patterns.

Extract the CRUD patterns, pagination, filtering, testing, and documentation template into separate bundle files (e.g., PATTERNS.md, TESTING.md) and reference them from a concise overview in SKILL.md.

Add an explicit sequenced workflow: e.g., '1. Define route → 2. Add validation → 3. Implement handler → 4. Test endpoint → 5. Verify error cases' with validation checkpoints at each step.

Reduce the main SKILL.md to under 80 lines by keeping only the route+validation+handler pattern as a single complete example, with pointers to detailed references.

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~250 lines, explaining many concepts Claude already knows well: HTTP status codes, CRUD patterns, basic Express middleware, pagination, filtering/sorting, and testing patterns. The HTTP status code list, response format examples, and security checklist are all standard knowledge that don't need to be spelled out. Much of this content could be cut by 70%+ without losing actionable value.	1 / 3
Actionability	The code examples are concrete, executable, and copy-paste ready. Route definitions, validation middleware, handler implementations, error handling, pagination, testing examples — all are complete and runnable JavaScript/Express code with specific patterns.	3 / 3
Workflow Clarity	The skill lists components to build (route, validation, auth, handler, error handling, docs, tests) but doesn't provide a clear sequenced workflow with validation checkpoints. There's no explicit 'build in this order, verify at each step' process — it's more of a reference catalog of patterns than a guided workflow.	2 / 3
Progressive Disclosure	The content is a monolithic wall of text with no bundle files to offload detailed patterns. The HTTP status codes, CRUD patterns, pagination, filtering, documentation template, and testing examples could all be in separate reference files. The references to related skills at the bottom are superficial and don't compensate for the lack of structural organization.	1 / 3
	Total	7 / 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: sickn33/antigravity-awesome-skills
Commit: 0839f85

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