CtrlK
BlogDocsLog inGet started
Tessl Logo

check-api

Audit SD.Next API route definitions and verify endpoint parameters plus request/response signatures against declared FastAPI contracts.

68

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The content is a well-structured, actionable audit procedure that respects token budget and assumes Claude's competence while providing concrete file targets, capture fields, and an ordered validation workflow. It is exemplary for an instruction-only skill with no external bundle dependencies.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what FastAPI, OpenAPI, or route registration are — and every section earns its place, matching the level-3 anchor despite minor title/intro restatement.

3 / 3

Actionability

Concrete, copy-paste-ready audit guidance is given throughout — named target files, exact fields to capture (path, methods, handler symbol, response_model, tags, auth flag), and specific flag conditions like "Required parameters that cannot be supplied by FastAPI" — so the instruction-only skill is fully actionable.

3 / 3

Workflow Clarity

A clearly sequenced six-step procedure mirrors the ordered Audit Goals, with an explicit runtime-validation gate and a static-fallback checkpoint in step 6 and severity-ordered reporting; this read-only audit does not require a destructive-feedback loop.

3 / 3

Progressive Disclosure

The skill is self-contained with no bundle files, and content is organized into well-signaled sections (When To Use, Primary File, Secondary Files, Audit Goals, Procedure, Reporting Format) with only one-level repo source references, matching the well-organized level-3 anchor.

3 / 3

Total

12

/

12

Passed

Description

67%

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 specific and distinct but lacks an explicit "Use when..." trigger clause, capping its completeness and leaving trigger-term coverage at a solid-but-incomplete level. It is a strong, narrowly-scoped description missing only explicit invocation guidance.

Suggestions

Add an explicit trigger clause such as "Use when auditing API correctness, reviewing changed API routes, or when OpenAPI docs or client schemas look wrong."

Broaden natural trigger terms to include user-facing phrasing like "OpenAPI", "API contract", and "schema mismatch" rather than only internal terminology.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Audit SD.Next API route definitions", "verify endpoint parameters", "verify... request/response signatures against declared FastAPI contracts" — matching the multi-action anchor rather than the domain-only level 2.

3 / 3

Completeness

It clearly answers "what" but contains no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Relevant technical terms are present (API routes, endpoints, parameters, request/response signatures, FastAPI contracts) but common natural variations a user would say ("OpenAPI", "schema mismatch", "API contract check") are missing, fitting the level-2 anchor.

2 / 3

Distinctiveness Conflict Risk

The SD.Next FastAPI route-auditing niche is distinct with specific triggers and is unlikely to overlap with other skills, matching the level-3 anchor.

3 / 3

Total

10

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
vladmandic/sdnext
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.