CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

77%

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

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 well-structured with a clear workflow and mostly executable code, but it is undermined by duplicated sections, a code typo, and dead references that point to files missing from the bundle. Tightening the redundancy and making every referenced path resolve would lift it substantially.

Suggestions

Remove the duplicated sections: keep authentication examples in one place (Step 2 or "Authentication Methods", not both), merge the two configuration blocks, and drop the inline error-status table in favor of the existing references/error-handling.md, along with the filler Overview and ✓-Features checklist.

Fix the dead references: references/rate-limiting.md, references/testing-apis.md, and the templates/ files (api-config-template.json, error-handler-template.js, retry-logic-template.js) do not exist in the bundle — either create them or remove the links and the Templates section.

Correct the "retryMult iplier" typo in the configuration example and show where APIClient comes from (an import or source note) so the code samples are copy-paste ready; consider folding the validation command into the workflow as an explicit step.

DimensionReasoningScore

Conciseness

The body is mostly code-driven rather than explaining known concepts, but it carries noticeable redundancy: auth examples appear in both Step 2 and the "Authentication Methods" section, configuration is shown in both Step 1 and "Complete Configuration Options", the error-status table duplicates references/error-handling.md, and the Overview plus ✓-Features checklist restate the description as filler. Version and last-updated stamps add time-sensitive tokens with no purpose.

3 / 5

Actionability

Concrete JavaScript snippets and a runnable validation command ("python scripts/validate-config.py config.json") cover the common cases, but "retryMult iplier: 2" is a typo that breaks the config example and APIClient is used with no import or source, so the code is not fully copy-paste ready.

4 / 5

Workflow Clarity

Steps 1-4 (Configure, Add Authentication, Make Requests, Handle Errors) are clearly sequenced and a validation checkpoint exists, but it sits in a separate "Validation" section outside the workflow sequence rather than integrated as a step with a verify-then-proceed loop.

4 / 5

Progressive Disclosure

References are clearly signaled and one level deep where they exist, but scored against the actual bundle, 4 of the referenced paths are dead: references/rate-limiting.md, references/testing-apis.md, and the entire templates/ directory (api-config-template.json, error-handler-template.js, retry-logic-template.js) do not exist. Error-handling content is also inlined despite a dedicated reference file.

3 / 5

Total

14

/

20

Passed

Description

83%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 that clearly states capabilities and provides an explicit, natural-language trigger clause. It is specific and complete, with only minor gaps in synonym coverage and capability enumeration.

DimensionReasoningScore

Specificity

Lists several specific actions ("authentication, error handling, retry logic, and request management" plus "OAuth, JWT, API keys"), but "request management" is generic and body-covered capabilities like rate limiting and logging are absent, leaving minor gaps in coverage.

4 / 5

Completeness

Explicitly answers both what ("REST API client builder with authentication, error handling, retry logic, and request management") and when ("Use when building API integrations, creating API clients, or working with REST services") with concrete trigger phrases in third-person voice.

5 / 5

Trigger Term Quality

Natural trigger phrases like "building API integrations", "creating API clients", and "working with REST services" are present, but common synonyms such as "REST API", "HTTP client", or "consuming an API" are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers (OAuth, JWT, REST client construction), but the broad API-integration space creates minor overlap risk with API testing, API design, or web-scraping skills.

4 / 5

Total

17

/

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.

Validation — 14 / 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

Path

skills/skill-builder-generic/examples/api-client-skill/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.