CtrlK
BlogDocsLog inGet started
Tessl Logo

api-client

REST API client builder with authentication, error handling, retry logic, and request management. Supports OAuth, JWT, API keys. Use when building API integrations, creating API clients, or working with REST services.

61

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 ./skills/skill-builder-generic/examples/api-client-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 action-oriented with good sequencing and one-level references, but suffers from redundant sections, a broken code token, validation that is not integrated as a workflow checkpoint, and several referenced bundle files that are missing.

Suggestions

Remove duplicated authentication content — keep it in references/authentication-guide.md and link once instead of inlining it in both Step 2 and the Authentication Methods section.

Fix the broken config token "retryMult iplier" (should be "retryMultiplier") and delete the separate ✓ Features list that restates the code examples.

Weave validation into the workflow as an explicit checkpoint (e.g., "Step 1.5: validate with python scripts/validate-config.py before making requests") and create the missing rate-limiting.md, testing-apis.md, and templates/ files referenced by the body.

DimensionReasoningScore

Conciseness

Mostly code with little concept-padding, but authentication is shown twice (Step 2 and "Authentication Methods"), the full config block repeats auth, the bottom References list duplicates in-body links, and the ✓ Features list restates the code — several redundant sections, more than minor.

3 / 5

Actionability

Concrete, mostly copy-paste-ready examples cover GET/POST/PUT/DELETE, setAuth, error handling, and full configuration, but the config block contains a broken token ("retryMult iplier") that prevents full executability.

4 / 5

Workflow Clarity

Steps 1–4 (Configure, Authenticate, Make Requests, Handle Errors) are clearly sequenced, but the validate-config.py step is a detached section rather than a checkpoint woven into the flow, leaving validation gaps and implicit checkpoints.

3 / 5

Progressive Disclosure

Section structure is reasonable and references are one level deep, but several referenced paths do not exist in the bundle (references/rate-limiting.md, references/testing-apis.md, templates/api-config-template.json), so navigation is broken for those entries.

3 / 5

Total

13

/

20

Passed

Description

88%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, third-person description that concretely states capabilities and gives explicit "Use when" triggers covering both what and when. Trigger-term synonym coverage and distinctiveness against adjacent API skills are the only minor gaps.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — "authentication, error handling, retry logic, and request management" plus "OAuth, JWT, API keys" — giving comprehensive coverage rather than a single vague action.

5 / 5

Completeness

It explicitly states what it does ("REST API client builder with…") and when to use it ("Use when building API integrations, creating API clients, or working with REST services") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"building API integrations, creating API clients, or working with REST services" are natural user phrases, but common synonyms like "calling an API" or "consuming an API" are missing, so it falls just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

"REST API client builder" is a clear niche, but the broad trigger "building API integrations" leaves minor overlap risk with other API-related skills, so it is mostly distinct rather than minimal-conflict.

4 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 missing

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

Repository
fernandezbaptiste/Skrillz
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.