api-endpoint-builder

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

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

65%Weight 40%Scale 1-5

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

The content is highly actionable with comprehensive executable examples, but it is verbose in places and presents as a long monolithic document with no progressive disclosure to separate reference material. Workflow sequencing would improve with explicit validation checkpoints.

Suggestions

Remove concept explanations Claude already knows — the HTTP status code list and 'Key Principles' section — to recover token budget.

Move the bulk code examples (full CRUD handlers, documentation template, testing example) into reference files under references/ and link to them from SKILL.md to improve progressive disclosure.

Turn the security checklist and tests into explicit gated steps in the endpoint build workflow (e.g. 'Run tests before considering the endpoint complete') to add validation checkpoints.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient executable code, but it explains concepts Claude already knows (the full HTTP status code list, a 'Key Principles' section restating obvious maxims) and re-implements overlapping handlers across sections, so it could be tightened.	3 / 5
Actionability	It provides fully executable, copy-paste-ready JavaScript covering the common cases: route definition, validation middleware, handler with hashing, centralized error handling, pagination, filtering, documentation template, and tests.	5 / 5
Workflow Clarity	A sequence exists via 'Endpoint Structure' steps 1-3, but validation checkpoints are not wired into the flow — testing is gated on 'if requested' and the security checklist is a separate appendix rather than a step gate.	3 / 5
Progressive Disclosure	Sections are well-organized with clear headers, but the ~320-line body is monolithic with no external reference files; extensive code examples and templates that could live in separate files are all inlined.	3 / 5
	Total	14 / 20 Passed

Description

58%Weight 40%Scale 1-5

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 uses correct third-person voice and names concrete capabilities, but lacks any explicit 'Use when...' trigger guidance, which caps completeness and limits trigger-term coverage. It is distinct and reasonably specific but would benefit from concrete trigger phrases.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g. 'Use when the user asks to create an API endpoint, build a REST API, add a route, or scaffold CRUD operations.'

Include natural synonyms users say ('route', 'web service', 'HTTP endpoint') to improve trigger-term coverage and reduce overlap with generic backend skills.

Drop the vague 'Follows best practices for security and scalability' in favor of another concrete capability (e.g. 'rate limiting') to raise specificity.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several concrete actions ('validation, error handling, authentication, and documentation'), though the trailing 'best practices for security and scalability' is generic fluff rather than an additional capability.	4 / 5
Completeness	It clearly answers 'what' (builds endpoints with validation, error handling, auth, documentation) but provides no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	'REST API endpoints' is a natural phrase a user would say, but the description omits common synonyms and variations users also say ('route', 'web service', 'HTTP', file extensions).	3 / 5
Distinctiveness Conflict Risk	'Builds production-ready REST API endpoints' carves a clear niche distinct from most skills, with only minor overlap risk against general backend/web-service skills.	4 / 5
	Total	14 / 20 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/agentic-awesome-skills
Path: skills/api-endpoint-builder/SKILL.md
Commit: b1aebac

Reviewed: ~15 hours 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.