CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

api-review

Review API endpoints for security, validation, error handling, and production readiness.

Quality

72%

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-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 maximally token-efficient and cleanly organized for a short checklist skill, but it stays at the level of generic reminders rather than actionable review guidance. Adding concrete examples (structured error format, validation approach, rate-limit check command) and a brief 'what to do when a check fails' loop would substantially improve it.

Suggestions

Add a concrete example for at least the highest-value checks — e.g., a structured error response JSON shape, or how to trace authentication middleware for a request.

Add a short verification/reporting step, e.g., 'When a check fails, note the issue with file:line and suggested fix, and re-review after remediation', to introduce a feedback loop.

Specify what 'suitable rate limiting' means concretely (e.g., per-IP/per-user token bucket thresholds) so the rate-limit check is executable rather than a judgment call.

DimensionReasoningScore

Conciseness

The body is a lean five-item checklist with zero padding and no explanation of concepts Claude already knows — every token earns its place. It matches the 'lean and efficient; assumes Claude's competence' anchor exactly.

5 / 5

Actionability

Each item is a high-level directive ('Validate all user-controlled input', 'Confirm expensive endpoints have suitable rate limiting') without concrete commands, code, or specifics on how to execute the check — matching the 'minimal concrete guidance; high-level hints' anchor. It is not 3 because nothing is executable or example-backed; it is not 1 because the items do tell Claude specifically what to check.

2 / 5

Workflow Clarity

The five steps are clearly enumerated and logically ordered, but there are no checkpoints or feedback loops (e.g., what to do when a check fails, how to report findings or re-review after fixes), matching the 'steps listed but validation gaps' anchor. It is not 4 because checkpoints are entirely absent rather than having only minor gaps.

3 / 5

Progressive Disclosure

The skill is well under 50 lines, no bundle files exist to reference, and the content is cleanly organized under a single heading with a numbered list, so the simple-skill guideline applies: well-organized short content with no need for external references scores 5.

5 / 5

Total

15

/

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.

A concise, third-person description with a specific 'what' and solid trigger keywords, but it omits any 'when to use' guidance, which caps its completeness. Adding a 'Use when...' clause with concrete trigger phrases would raise it to the top tier.

Suggestions

Add an explicit trigger clause, e.g., 'Use when reviewing or auditing API endpoints, REST routes, or new backend services before merge/deployment.'

Include common synonyms and variations users would say, such as 'REST API', 'endpoint audit', or 'review my endpoints', to broaden natural trigger coverage.

Optionally name one or two more concrete review actions (e.g., 'check authentication, authorization, input validation') to push specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

The description names the domain ('API endpoints') and lists several concrete review areas ('security, validation, error handling, and production readiness'), matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because the areas are categories rather than concrete actions and coverage is not comprehensive (e.g., no mention of auth configuration, dependency review, or testing).

4 / 5

Completeness

The 'what' is clear ('Review API endpoints for security, validation, error handling, and production readiness') but there is no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the judging guidelines. It is not 4 because the 'when' is entirely absent rather than merely implicit; it is not 2 because the 'what' is specific and concrete.

3 / 5

Trigger Term Quality

'API endpoints', 'security', 'error handling', and 'validation' are natural phrases users would say, giving good keyword coverage. A few natural terms are missing (e.g., 'REST', 'audit', 'review my API'), keeping it below the comprehensive-synonym anchor of 5.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear API-review niche that is mostly distinct, with only minor overlap risk against closely related skills like general code review or security review. It is not 5 because those adjacent review skills could plausibly trigger for overlapping requests (e.g., 'check this code for security').

4 / 5

Total

15

/

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/checkout-service

Path

.agents/skills/api-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.