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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/api-endpoint-builder/SKILL.md

The canonical home for this skill is api-endpoint-builder in sickn33/agentic-awesome-skills

Quality

Content

57%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 body delivers actionable, executable code examples across the common endpoint cases but is padded with concepts Claude already knows, lacks validation checkpoints in its destructive CRUD workflow, and inlines bulk content that could be externalized.

Suggestions

Add an explicit validation/verification checkpoint to the CRUD workflow (e.g. run tests or validate the request before committing destructive changes) to lift workflow clarity past the destructive-operation cap.

Remove the 'HTTP Status Codes' list and 'Key Principles' section — both restate knowledge Claude already has — to improve token efficiency.

Move the full documentation template and testing example into a separate reference file (e.g. references/DOCUMENTATION.md) and link to it from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with useful code, but the 'HTTP Status Codes' list and the 'Key Principles' bullet list restate concepts Claude already knows, fitting 'mostly efficient but includes some unnecessary explanation'; not a 2 because the bulk is concrete code rather than padded prose.	3 / 5
Actionability	Provides concrete, mostly copy-paste-ready JavaScript for routing, validation, handlers, pagination, and tests, with minor gaps (authenticate, db, bcrypt, request(app) are referenced but not defined), matching 'mostly executable guidance; minor gaps'; not a 5 due to those undefined references.	4 / 5
Workflow Clarity	The endpoint-structure sections and 'What You'll Build' list give a rough sequence, but there are no validation checkpoints, and because CRUD includes destructive operations (DELETE) the guideline caps workflow clarity at 3.	3 / 5
Progressive Disclosure	There are no bundle files and the content is well-sectioned, but at ~310 lines substantial content (full example handlers, documentation template, testing example) is inlined that could live in separate references, fitting 'some structure but content that should be separate is inline'; not a 4 because organization gaps remain and nothing is split out.	3 / 5
	Total	13 / 20 Passed

Description

66%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 clearly states what the skill does and names several concrete capabilities with decent natural trigger terms, but it lacks any explicit 'when to use' guidance, capping completeness at 3.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to create an API endpoint, build a REST API, or add routes to a backend service.'

Include common synonyms such as 'route', 'controller', or 'web service' to broaden natural trigger coverage.

Trim the vague 'Follows best practices for security and scalability' in favor of another concrete capability like 'testing' or 'response formatting'.

Dimension	Reasoning	Score
Specificity	Names the domain (REST API endpoints) and lists several concrete actions — 'validation, error handling, authentication, and documentation' — with only minor coverage gaps (testing/routing not mentioned), matching the 'lists several specific actions; minor gaps' anchor; not a 5 because coverage is not comprehensive.	4 / 5
Completeness	Provides a clear 'what' (builds production-ready REST API endpoints with validation, error handling, authentication, documentation) but no 'Use when...' clause or explicit trigger guidance, so per the judging guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	Includes natural terms a user would say ('REST API endpoints', 'API') with good coverage, but misses common synonyms like 'route', 'web service', or 'controller', fitting 'good keyword coverage; a few natural terms missing' rather than the comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	The REST-API-endpoint-builder niche is mostly distinct with clear triggers, though it has minor overlap risk with general backend or framework-specific skills, matching 'mostly distinct; minor overlap risk' rather than the fully distinct 5.	4 / 5
	Total	15 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/api-endpoint-builder/SKILL.md
Commit: 900c504

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