api-endpoint-builder
Builds production-ready REST API endpoints with validation, error handling, authentication, and documentation. Follows best practices for security and scalability.
52
41%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/api-endpoint-builder/SKILL.mdQuality
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 API development) and lists relevant concerns, but it reads more like a feature checklist than a precise skill description. It critically lacks a 'Use when...' clause, making it difficult for Claude to know when to select this skill over others. The trailing sentence about 'best practices for security and scalability' is vague filler that doesn't aid skill selection.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user asks to create API routes, build REST endpoints, set up CRUD operations, or scaffold a web API.'
Replace vague phrases like 'Follows best practices for security and scalability' with concrete actions such as 'Implements rate limiting, input sanitization, JWT/OAuth authentication, and generates OpenAPI/Swagger documentation.'
Include common user-facing trigger terms and variations like 'API route', 'CRUD', 'HTTP endpoint', 'Express', 'FastAPI', 'Django REST', 'Swagger', 'OpenAPI' to improve matching across frameworks and terminology.
| 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 particular operations like 'create CRUD endpoints', 'generate OpenAPI specs', or 'implement JWT auth'. | 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 'when' is entirely absent, warranting a score of 1. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'REST API', 'endpoints', 'authentication', 'validation' that users might mention, but misses common variations like 'API route', 'HTTP endpoint', 'middleware', 'CRUD', 'Express', 'FastAPI', 'swagger', or file extensions. Coverage is partial. | 2 / 3 |
Distinctiveness Conflict Risk | 'REST API endpoints' provides some specificity, but terms like 'validation', 'error handling', 'authentication', 'security', and 'scalability' are extremely broad and could overlap with many backend development, web framework, or security-related skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
50%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 main strength. However, it is significantly over-verbose, explaining many concepts Claude already knows (HTTP status codes, CRUD conventions, basic security practices). The content would benefit greatly from trimming to only project-specific conventions and splitting reference material into separate files.
Suggestions
Remove or drastically condense the HTTP status codes list, security checklist, and 'Key Principles' section — Claude already knows these. Focus only on project-specific conventions that differ from standard practices.
Split reference material (common patterns, documentation template, testing example) into separate linked files to improve progressive disclosure and reduce the main file's token footprint.
Add explicit validation/verification steps to the workflow, such as 'test the endpoint with curl after implementation' or 'verify authentication middleware is working before adding business logic'.
Condense the 'When to Use This Skill' trigger list — 'User asks to create an API endpoint' is sufficient without listing every synonym.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose for what it teaches. The HTTP status codes list, security checklist, response format patterns, CRUD conventions, and key principles are all things Claude already knows well. The skill is ~200 lines of content that could be condensed to ~50 lines of project-specific conventions and patterns. | 1 / 3 |
Actionability | All code examples are fully executable JavaScript/Express code that can be directly used. Validation, handler implementation, pagination, filtering, testing, and documentation examples are all copy-paste ready with concrete implementations. | 3 / 3 |
Workflow Clarity | The 'What You'll Build' section lists components to create and the numbered sections (1-3) provide a sequence, but there are no explicit validation checkpoints or feedback loops. For building API endpoints that interact with databases and handle authentication, there should be verification steps (e.g., test the endpoint, validate the schema). | 2 / 3 |
Progressive Disclosure | The content is a monolithic document with everything inline. The HTTP status codes reference, security checklist, common patterns, and testing examples could all be split into separate reference files. The 'Related Skills' section at the end shows awareness of linking but the main content itself is not well-layered. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%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
6f67640
- Reviewed
Table of Contents
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.