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

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./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 high level without specifying concrete actions or frameworks. The biggest weakness is the complete absence of a 'Use when...' clause, making it hard for Claude to know when to select this skill over others. The buzzword-heavy tail ('best practices for security and scalability') adds little discriminative value.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'Use when the user asks to create an API endpoint, build a REST service, add a route, or scaffold CRUD operations.'

Replace vague phrases like 'Follows best practices for security and scalability' with concrete actions such as 'Adds input validation schemas, rate limiting, JWT/OAuth middleware, and generates OpenAPI/Swagger documentation.'

Include common user-facing keywords and variations: 'API route', 'HTTP endpoint', 'CRUD', 'Express', 'FastAPI', 'Django REST', '.json', 'Swagger' 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, add JWT middleware.'	2 / 3
Completeness	Describes what it does (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 the 'what' portion is also somewhat vague, placing this at 1.	1 / 3
Trigger Term Quality	Includes relevant terms like 'REST API', 'endpoints', 'authentication', 'validation' that users might naturally say, but misses common variations like 'API route', 'HTTP endpoint', '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', 'security', and 'scalability' are broad enough to overlap with general backend development, security, or code quality 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 reads more like a comprehensive Express.js REST API tutorial than a concise skill file for Claude. It contains substantial content Claude already knows (HTTP status codes, CRUD patterns, basic security practices) and would benefit enormously from trimming to only project-specific conventions and splitting detailed patterns into referenced files. The code examples are its strongest asset—they are concrete, executable, and well-structured.

Suggestions

Remove 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.

Split detailed patterns (CRUD, pagination, filtering, testing, documentation template) into separate reference files and link to them from a concise overview section.

Add explicit validation/verification steps: e.g., 'After creating the endpoint, run the test suite to verify' or 'Verify the route is registered by checking the route table.'

Reduce the skill to ~50-80 lines covering: the expected response format convention, the authentication middleware pattern, and links to detailed examples in separate files.

Dimension	Reasoning	Score
Conciseness	Extremely verbose for a Claude skill. Explains basic concepts Claude already knows well (HTTP status codes, CRUD operations, what pagination is, how bcrypt works). The HTTP status code list, security checklist, and key principles section are all things Claude has deep knowledge of. This is more of a tutorial than a skill file.	1 / 3
Actionability	All code examples are fully executable JavaScript/Express code that is copy-paste ready. Validation, handler implementation, pagination, filtering, testing, and documentation templates are all concrete and complete.	3 / 3
Workflow Clarity	The numbered sections (1. Route Definition, 2. Input Validation, 3. Handler Implementation) provide a sequence, but there are no validation checkpoints or feedback loops. No guidance on verifying the endpoint works after building it, no explicit 'test before deploying' step, and no error recovery workflow.	2 / 3
Progressive Disclosure	This is a monolithic wall of content (~200+ lines) with no references to external files. The CRUD patterns, pagination, filtering, testing, and documentation template sections could all be split into separate reference files. Everything is inlined, making the skill heavy to load into context.	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: 1a9f5ac

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