CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

up-to-date

Use when writing, editing, or refactoring code that calls any third-party SDK, API, or library; installing or importing external packages; debugging when an API call returns success but the expected side-effect doesn't happen; hitting 4xx errors from an external API; or when something 'doesn't work' and the code involves an external service.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 a well-structured, actionable behavioral rule with concrete commands, a clear four-step workflow, validation checkpoints, and properly separated bundle files. Its only weaknesses are mild repetition of the core rule and trigger lists that duplicate the frontmatter.

Suggestions

Trim the repeated 'do NOT write from memory' admonitions to a single statement to tighten conciseness.

Spell out the Context7 invocation (tool name plus example query) instead of the 'resolve-library-id → query-docs' shorthand.

Add one line to step 4 telling the agent to loop back to step 2's doc comparison if the build or live test fails.

DimensionReasoningScore

Conciseness

Mostly lean with non-obvious, high-value advice ('A 200 with a valid-looking response body can still mean nothing happened'), but the core rule is repeated ('fetch the real documentation first', 'Do NOT write integration code from memory. Do NOT diagnose failures from memory') and 'When This Triggers' largely duplicates the frontmatter description.

4 / 5

Actionability

Provides concrete executable commands (cat node_modules/<pkg>/package.json | grep '"version"'; python3 scripts/check_versions.py npm resend) and a specific code-vs-docs comparison checklist. Not 5 because 'resolve-library-id → query-docs' is abbreviated tool shorthand rather than an executable invocation.

4 / 5

Workflow Clarity

Four mandatory steps are clearly sequenced with validation checkpoints (compare code vs docs, build to verify types, test live and verify the downstream effect) and the decision flowchart gives error-recovery branches. Not 5 because there is no explicit loop-back instruction when post-change verification fails.

4 / 5

Progressive Disclosure

SKILL.md serves as a clear overview while bulk material is correctly split into references/doc-urls.md and scripts/check_versions.py — both real files, one level deep, each introduced with what it does and when to consult it. Navigation is easy and the split is appropriate.

5 / 5

Total

17

/

20

Passed

Description

52%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.

The description has strong, natural trigger coverage but is missing the capability statement entirely — a reader cannot tell what the skill does, only when it fires. This caps completeness and specificity despite excellent trigger phrasing.

Suggestions

Add a leading 'what' clause stating the skill's action, e.g. 'Fetches current API documentation and checks dependency versions before writing or debugging third-party integration code.'

Mention the bundled resources (version-check script, curated doc-URL reference) in the description to add concrete capability specifics.

Add one or two common synonyms such as 'upgrading' or 'migrating' dependencies to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('any third-party SDK, API, or library') and concrete trigger scenarios, but states no capability actions — what the skill actually does (fetch current docs, check versions) is never stated. Not 4 because no actions are listed; not 2 because the trigger scenarios are concrete rather than generic.

3 / 5

Completeness

Only the 'when' is present — the description is entirely trigger clauses with no 'what' stating what the skill does. This matches the anchor 'only when is present without what'; the unusually detailed triggers do not substitute for the missing capability statement.

2 / 5

Trigger Term Quality

Includes natural phrases users would actually say: "something 'doesn't work'", 'hitting 4xx errors', 'returns success but the expected side-effect doesn't happen', 'installing or importing external packages'. Not 5 because common synonyms ('upgrade', 'migrate') and package-manager names (npm, pip) are absent.

4 / 5

Distinctiveness Conflict Risk

The niche (external API/SDK integration) has distinct triggers ('hitting 4xx errors', 'success but the expected side-effect doesn't happen') making it mostly distinct. Not 5 because 'doesn't work' and 'external service' are broad enough to overlap with general debugging skills.

4 / 5

Total

13

/

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

LeonMelamud/up-to-date-skill

Path

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.