CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

api-safety-review

Review backend API endpoints for security, validation, errors, and safe production behaviour.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/api-safety-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 an exceptionally lean, well-ordered review checklist with no wasted tokens and appropriate structure for a short single-purpose skill. Its main weakness is actionability: the checks name categories without concrete indicators, so execution depends entirely on the model's prior knowledge.

Suggestions

Add one or two concrete indicators per step (e.g. which auth headers to check, expected 401/403 distinctions, or examples of errors that leak stack traces) to make the checks executable rather than directional.

Add a brief note on output — e.g. report findings per endpoint with severity — so the workflow closes with what to do when a check fails.

DimensionReasoningScore

Conciseness

The ten-line body has no padding and no explanation of concepts Claude already knows; each of the five checklist lines earns its tokens.

5 / 5

Actionability

As an instruction-only skill the missing code is not penalized, but directives like 'Verify authentication is enforced' and 'Validate all externally supplied input' state what to check without any specifics of how (no example headers, status codes, or common failure patterns), leaving key details missing.

3 / 5

Workflow Clarity

A clear numbered sequence ordered sensibly (authentication, authorization, input, errors, idempotency) where each step is itself a verification; minor gaps remain because the skill never says how to report findings or what to do when a check fails.

4 / 5

Progressive Disclosure

The skill is under 50 lines, has no need for external references (none exist in the bundle), and its heading plus numbered list is well-organized — the simple-skill exception applies.

5 / 5

Total

17

/

20

Passed

Description

53%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 is concise, in third person, and names a specific domain with relevant security keywords, but it omits any 'use when' trigger guidance and only implies its actions through a list of topics. Adding an explicit trigger clause and one or two concrete review actions would raise completeness, specificity, and trigger-term quality together.

Suggestions

Add an explicit 'when' clause, e.g. 'Use when reviewing or auditing backend API endpoints, REST routes, or handlers before deployment', to lift completeness above the 3 cap.

Include natural user synonyms such as 'audit', 'harden', or 'vulnerability' so trigger terms match how users actually phrase the request.

Sharpen the 'what' with a concrete action or two beyond the single verb 'Review' (e.g. 'Check endpoints for missing authentication, unsafe input validation, and information-leaking errors').

DimensionReasoningScore

Specificity

Names the domain ('backend API endpoints') and topical areas ('security, validation, errors, and safe production behaviour'), but contains only one action verb ('Review') — the listed items are topics to examine rather than several distinct concrete actions.

3 / 5

Completeness

The 'what' is clear ('Review backend API endpoints for security, validation, errors, and safe production behaviour') but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Relevant natural keywords like 'API', 'security', 'backend', and 'errors' are present, but common user phrasings such as 'audit', 'harden', 'vulnerability', or 'API review' are missing, matching 'some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

'Review backend API endpoints' defines a narrow scope comparable in specificity to anchor 4's example, with only minor overlap risk against generic code-review or security-review skills; it lacks the explicit trigger phrases needed for 5.

4 / 5

Total

13

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

deesumblip/payments-api

Path

.agents/skills/api-safety-review/SKILL.md

Reviewed

Table of Contents

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.