api-endpoint-builder

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

Quality

60%

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/skills/api-endpoint-builder/SKILL.md

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

Quality

Content

61%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 is highly actionable with concrete Express examples and good section organization, but it is padded with concepts Claude already knows (HTTP status codes, restated principles) and lacks an explicit validation/verification checkpoint in the build workflow. Tightening the redundant sections and adding a 'verify the endpoint works' step would materially raise quality.

Suggestions

Remove or compress the 'HTTP Status Codes' list and 'Key Principles' section, which restate knowledge Claude already has and duplicate the code examples.

Add an explicit validation/verification checkpoint to the endpoint build flow (e.g., 'After implementing, run the test suite / send a sample request to confirm the endpoint behaves correctly').

Define or stub the `db` data layer and `authenticate` middleware so the code examples are fully copy-paste runnable, or note the abstraction explicitly.

Dimension	Reasoning	Score
Conciseness	Mostly efficient code, but the 'HTTP Status Codes' list (200/201/400/…) restates knowledge Claude already has and the 'Key Principles' section repeats what the code already demonstrates; fits anchor 3 (some unnecessary explanation that could be trimmed).	3 / 5
Actionability	Concrete, mostly executable Express code throughout (validation, handler, error handler, pagination, tests); minor gaps keep it at anchor 4 — `db.users` and the `authenticate` middleware are referenced but undefined abstractions.	4 / 5
Workflow Clarity	A sequence exists (route definition → input validation → handler) but there is no explicit verify/test checkpoint in the build flow; because the skill involves database writes (CRUD/DELETE), the rubric caps workflow_clarity at 3 for missing feedback loops.	3 / 5
Progressive Disclosure	Single self-contained file with well-organized section headers and no nested references; matches anchor 4 (good structure, minor organization gaps) — not 5 because nothing is split out and ~315 lines are all inline.	4 / 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 states concrete capabilities clearly but omits any 'when to use' trigger guidance, which caps completeness, and its trigger-term variety is limited. It is distinct and reasonably specific but would benefit from explicit use-when phrasing and more synonyms.

Suggestions

Add an explicit 'Use when...' clause listing trigger phrases (e.g., 'Use when the user asks to create an API endpoint, build a REST API, add a route, or implement CRUD operations').

Broaden trigger terms with natural synonyms users say — 'routes', 'CRUD', 'backend endpoints' — to improve trigger-term coverage.

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

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('validation, error handling, authentication, and documentation') matching anchor 4; not 5 because coverage is not comprehensive (testing/CRUD absent) and 'best practices for security and scalability' is vague padding.	4 / 5
Completeness	Clear 'what' (builds endpoints with validation, auth, etc.) but no 'Use when...' or equivalent trigger guidance; per rubric guideline a missing trigger clause caps completeness at 3, matching anchor 3.	3 / 5
Trigger Term Quality	'REST API endpoints' is a natural phrase users say, but keyword variety is thin with no common synonyms (routes, CRUD, backend); fits anchor 3 (some relevant keywords, missing variations) rather than 4.	3 / 5
Distinctiveness Conflict Risk	'REST API endpoints' carves a fairly distinct niche with only minor overlap risk against general backend/web skills, matching anchor 4; not 5 because the scope is still somewhat broad.	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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/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.