api-endpoint-builder
Builds production-ready REST API endpoints with validation, error handling, authentication, and documentation. Follows best practices for security and scalability.
49
37%
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 list than an actionable skill description. The absence of a 'Use when...' clause is a significant gap that would make it harder for Claude to know when to select this skill. The buzzword-heavy tail ('best practices for security and scalability') adds little discriminative value.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user asks to create API endpoints, build a REST service, add routes, or set up CRUD operations.'
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 file/framework references like 'Express', 'FastAPI', 'Django REST', 'API routes', 'HTTP methods', 'CRUD' to improve matching against natural user requests.
| 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', 'CRUD', 'middleware', 'Express', 'FastAPI', 'swagger', or specific framework names that users would naturally say. | 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, web framework, 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 is highly actionable with complete, executable code examples, but it's far too verbose for a Claude skill—most of the content covers standard REST API knowledge that Claude already possesses (HTTP status codes, CRUD patterns, bcrypt usage). The content would benefit enormously from being trimmed to only project-specific conventions and patterns, with reference material split into separate files.
Suggestions
Remove the HTTP status codes list, security checklist items, and 'Key Principles' section—Claude already knows these. Focus only on project-specific conventions (e.g., your specific response format, your specific auth middleware pattern).
Split content into separate files: move CRUD patterns, pagination/filtering examples, testing templates, and documentation templates into referenced files (e.g., PATTERNS.md, TESTING.md).
Add explicit workflow validation steps: after building an endpoint, include a checkpoint to run tests or verify the endpoint responds correctly before moving on.
Reduce the skill to a concise overview (~50 lines) covering: the required response format, the middleware chain order, and links to detailed pattern 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. The content is ~200 lines when it could be ~50 lines of project-specific conventions. | 1 / 3 |
Actionability | All code examples are fully executable JavaScript/Express code that could be copy-pasted. Includes complete handler implementations, validation middleware, test examples, and documentation templates with concrete syntax. | 3 / 3 |
Workflow Clarity | The endpoint structure sections (1-3) provide a reasonable sequence for building an endpoint, but there are no explicit validation checkpoints or feedback loops. For example, there's no step to verify the endpoint works after creation, no mention of testing the validation logic, and no error recovery guidance. | 2 / 3 |
Progressive Disclosure | Monolithic wall of content with everything inline. The HTTP status codes reference, security checklist, CRUD patterns, pagination, filtering, testing, and documentation templates could all be in separate referenced files. The skill mentions related skills at the bottom but doesn't split its own content appropriately. | 1 / 3 |
Total | 7 / 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
7241463
- 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.