CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

api-development

Design, build, secure, document, and maintain robust RESTful and GraphQL APIs. Use when architecting API resource endpoints, implementing authentication and authorization (JWT, OAuth 2.0, API keys, RBAC/ABAC), handling pagination, filtering, and caching, standardizing error formats (RFC 7807), enforcing rate limits, authoring OpenAPI/Swagger specs, designing webhooks, or configuring CORS and security headers.

66

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

63%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 highly actionable with production-grade, executable code and a solid verification section, but it is token-heavy: large portions restate standard HTTP knowledge Claude already has, and detailed implementations that belong in the reference bundle are inlined in SKILL.md. Restructuring toward a lean overview with deeper offloading to references would materially improve it.

Suggestions

Remove or drastically compress the standard HTTP status code table and method safety/idempotency matrix (Steps 1.2–1.3) — Claude already knows these; keep only the project-specific choices (e.g., 'we use 422 for semantic validation failures, RFC 7807 for all errors').

Move the full middleware implementations that the reference file already covers in more depth (rate limiter, pagination, JWT/auth code, GraphQL DataLoader) into references/rest-graphql-patterns.md, leaving SKILL.md as a concise decision guide that says which pattern to apply and links to the implementation.

Trim definitional prose such as 'Webhooks provide asynchronous event notifications pushed to consumer endpoints over HTTP POST' and the introductory paragraph on what API development is; assume Claude's knowledge and keep only the operative conventions.

DimensionReasoningScore

Conciseness

The ~800-line body inlines substantial textbook knowledge Claude already has: an 18-row standard HTTP status code table, an HTTP method safety/idempotency matrix ('GET ... Retrieve resource representation'), generic algorithm explanations ('Token Bucket: Accumulates tokens up to capacity', 'Webhooks provide asynchronous event notifications pushed to consumer endpoints over HTTP POST'), and an introductory paragraph defining what API development is. This is noticeably verbose with several unnecessary explanations, fitting anchor 2 rather than 3.

2 / 5

Actionability

The body provides complete, executable guidance: full TypeScript middleware (permission checks, sliding-window Redis rate limiter, ETag conditional requests, Zod schema validation, HMAC-SHA256 webhook signing with replay protection), a complete OpenAPI 3.1 YAML template, and copy-paste curl verification commands. Code is copy-paste ready and covers the common cases, matching the top anchor.

5 / 5

Workflow Clarity

Steps 1–13 are clearly sequenced and a dedicated Verification section provides explicit checks with expected outputs ('HTTP/1.1 304 Not Modified', '0 errors, 0 warnings'). It falls short of anchor 5 because there are no error-recovery feedback loops (what to do when a check fails) and the 13 'steps' are parallel design areas rather than a strict execution order with checkpoints.

4 / 5

Progressive Disclosure

A single one-level-deep reference (references/rest-graphql-patterns.md, verified to exist) is clearly signaled in a 'Detailed Reference Material' section, but the SKILL.md body itself inlines ~800 lines of full code implementations — including topics the reference file covers in more depth (rate limiters, pagination, JWT, GraphQL) — that belong in the bundle. 'Content that should be separate is inline' fits anchor 3 better than anchor 4.

3 / 5

Total

14

/

20

Passed

Description

96%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 strong description: third-person voice, concrete capability verbs, an explicit 'Use when...' trigger clause with specific technologies, and no fluff or over-claims. The only weakness is that the broad API-development domain carries minor overlap risk with closely related skills.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions ('Design, build, secure, document, and maintain robust RESTful and GraphQL APIs') paired with named technologies (JWT, OAuth 2.0, RBAC/ABAC, RFC 7807, OpenAPI/Swagger, CORS), giving comprehensive coverage. It matches the 'multiple specific concrete actions; comprehensive coverage' anchor rather than 4, since there are no meaningful gaps in the actions claimed.

5 / 5

Completeness

It explicitly answers both 'what' (design, build, secure, document, and maintain RESTful and GraphQL APIs) and 'when' via a literal 'Use when...' clause enumerating concrete trigger scenarios. This is the exact pattern of the top anchor, not merely 'when could be more explicit' (score 4).

5 / 5

Trigger Term Quality

Natural trigger phrases a user would actually say are well covered: 'API resource endpoints', 'authentication and authorization', 'pagination, filtering, and caching', 'rate limits', 'OpenAPI/Swagger specs', 'webhooks', 'CORS and security headers', with synonyms (OpenAPI/Swagger). This matches the comprehensive-coverage anchor, including synonym variants.

5 / 5

Distinctiveness Conflict Risk

Technology-specific triggers (RFC 7807, OpenAPI, webhooks, CORS, RBAC/ABAC) make it unlikely to fire for unrelated skills, but the broad 'RESTful and GraphQL APIs' domain overlaps with closely related skills (framework-specific API skills, web-security skills, or LLM-API usage skills triggered by the generic word 'API'). Mostly distinct with minor overlap risk — anchor 4 rather than 5.

4 / 5

Total

19

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (802 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

administrakt0r/pro-skills-repo-administraktor

Path

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