add-api-endpoint

Add an endpoint to the backend.

Quality

34%

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 ./review-plugin-creator/evals/derive-rubric-from-evidence/inputs/target-skill/SKILL.md

Quality

Content

43%

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

This skill is extremely thin—it reads more like a high-level checklist than actionable guidance. It lacks concrete code examples, specific Fastify patterns (e.g., route registration, schema definition syntax), and any validation or testing steps. While concise, it sacrifices nearly all actionability and workflow clarity.

Suggestions

Add a concrete, executable Fastify route example showing route registration, request/response schema definition, and handler implementation.

Specify how to test the endpoint (e.g., a curl command, a test file pattern, or a Fastify inject example).

Clarify 'Make sure the types are in sync' with a specific step—e.g., running a type-check command or referencing a shared types file.

Include a validation checkpoint such as running the dev server and hitting the endpoint to confirm it works before considering the task complete.

Dimension	Reasoning	Score
Conciseness	The content is brief and doesn't over-explain concepts Claude already knows. However, the opening line 'Add a new API endpoint to the Fastify backend' slightly restates what the skill title/description already conveys.	4 / 5
Actionability	The steps are entirely high-level directions with no concrete code, commands, file naming conventions, schema examples, or specific Fastify patterns. There is nothing executable or copy-paste ready.	2 / 5
Workflow Clarity	A rough sequence of steps is present but they are poorly defined—'Make sure the types are in sync' and 'Test it' are vague with no validation checkpoints, no commands, and no feedback loops for verifying correctness.	2 / 5
Progressive Disclosure	The content is short and doesn't need external files, but it also lacks any structure beyond a single heading and a numbered list. No references to project conventions, example files, or related resources are provided, which would help for a skill of this nature.	3 / 5
	Total	11 / 20 Passed

Description

25%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is extremely terse and vague, providing only a single generic action ('add an endpoint') without specifying the technology, framework, or context. It lacks a 'Use when...' clause, natural trigger terms, and any detail that would help Claude distinguish this skill from other backend-related skills in a large skill library.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases such as 'Use when the user asks to create a new API route, REST endpoint, or add a handler to the backend server.'

Specify the technology stack or framework (e.g., Express, Django, FastAPI) and list concrete actions like 'creates route handler, adds request validation, registers middleware, updates route configuration.'

Include natural keywords and synonyms users would say: 'API route', 'REST endpoint', 'HTTP handler', 'controller', 'route', along with relevant HTTP methods like GET, POST, PUT, DELETE.

Dimension	Reasoning	Score
Specificity	Names a domain (backend endpoint) but the action is minimal and generic — 'add an endpoint' is a single vague action with no detail about what kind of endpoint, what framework, or what steps are involved.	2 / 5
Completeness	Has a very vague 'what' (add an endpoint to the backend) and completely lacks any 'when' clause or trigger guidance. The missing 'Use when...' clause caps this at 3 per the rubric, and the weak 'what' brings it to 2.	2 / 5
Trigger Term Quality	Contains 'endpoint' and 'backend' which are somewhat relevant keywords, but misses natural user phrases like 'API route', 'REST', 'controller', 'route handler', specific framework names, or HTTP methods.	2 / 5
Distinctiveness Conflict Risk	Very broad — 'add an endpoint to the backend' could overlap with any backend development skill, API skill, or web framework skill. There is nothing to distinguish this from other backend-related skills.	2 / 5
	Total	8 / 20 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: tesslio/product-plugins
Path: review-plugin-creator/evals/derive-rubric-from-evidence/inputs/target-skill/SKILL.md
Commit: be99f0b

Reviewed: 1 day 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.