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

36%Scale 1-5

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 provides a vague four-step outline with no concrete code, commands, file examples, or schema patterns. While it is concise, it sacrifices all actionability in the process. To be useful, it needs executable examples of route handlers, schema definitions, and specific testing commands.

Suggestions

Add a concrete, copy-paste-ready example of a Fastify route handler file under `src/routes/` with request/response schema definitions.

Specify how to 'make sure the types are in sync'—provide a concrete command or pattern (e.g., generating types from schemas, or referencing a shared types file).

Replace 'Test it' with specific testing guidance: a curl command, a test file example, or a command like `npm test`.

Include an example of the expected file structure and naming conventions for new endpoints.

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, a minor redundancy.	4 / 5
Actionability	The guidance is entirely vague and abstract—no concrete code, no specific file naming conventions, no schema examples, no commands. Every step is a high-level description rather than an executable instruction.	1 / 5
Workflow Clarity	A rough sequence of four steps is present, but steps are poorly defined (e.g., 'Make sure the types are in sync' and 'Test it' are vague with no validation checkpoints or concrete commands). There are no feedback loops or error recovery guidance.	2 / 5
Progressive Disclosure	The content is short enough that it doesn't need external files, but it also lacks any structure beyond a single heading and numbered list. No references to examples, schemas, or supporting files are provided, though the simplicity of the content means this is a moderate rather than severe issue.	3 / 5
	Total	10 / 20 Passed

Description

32%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.

This description is extremely terse and lacks the detail needed for effective skill selection. It provides only a single generic action without specifying the technology stack, the types of endpoints, or when this skill should be chosen. It would benefit greatly from concrete actions, trigger terms, and explicit usage guidance.

Suggestions

Add a 'Use when...' clause with trigger terms like 'API endpoint', 'route', 'REST', 'handler', 'new endpoint', or specific framework names (e.g., Express, FastAPI, Django).

Expand the 'what' to include specific actions such as the framework used, types of endpoints supported (CRUD, webhooks, etc.), and any related tasks like validation, middleware, or documentation.

Include file extensions or technology-specific terms (e.g., '.py', '.ts', 'router', 'controller') to improve distinctiveness and reduce conflict with other backend-related skills.

Dimension	Reasoning	Score
Specificity	Names the 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 minimal 'what' (add an endpoint to the backend) but no 'when' clause at all. The description doesn't explain when Claude should select this skill over others.	2 / 5
Trigger Term Quality	Contains 'endpoint' and 'backend' which are relevant keywords a user might say, but misses common variations like 'API', 'route', 'REST', 'handler', 'controller', or specific framework names.	3 / 5
Distinctiveness Conflict Risk	Very broad - 'add an endpoint to the backend' could overlap with many backend-related skills (API design, routing, middleware, database integration, etc.) without distinguishing what makes this skill unique.	2 / 5
	Total	9 / 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: 37f0a21

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.