CtrlK
BlogDocsLog inGet started
Tessl Logo

version-check

Recommend which Claude Code version to run, or whether to update. Use when asked which Claude Code version is best/safe, whether to update now, whether a recent release is buggy, or what changed since the installed version.

72

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A high-quality, actionable skill body: executable commands, a clearly sequenced workflow with explicit verification steps, and well-organized self-contained sections. The only dimension short of the top mark is conciseness, where a few heuristic explanations could be tightened.

DimensionReasoningScore

Conciseness

The body is dense with Claude-Code-specific heuristics Claude would not already know and avoids explaining basic concepts, with only minor prose in the heuristics section that could be trimmed; not 5 because a few explanatory clauses (e.g. the stable-vs-LTS framing) run slightly long, and not 3 because the bulk of every section earns its tokens.

4 / 5

Actionability

It provides copy-paste-ready, fully executable commands throughout — `claude --version`, `npm view ... dist-tags --json`, `gh api search/issues` with concrete jq filters, the `modelUsage` probe — covering the common cases completely; not below 5 because the examples are specific and runnable rather than pseudocode.

5 / 5

Workflow Clarity

A clearly numbered 1-5 sequence (installed vs published, changelog scan, community sentiment, test the claim, recommend) with explicit validation checkpoints — "Re-run the same command after updating to confirm the number moved" and "confirm with `claude --version` afterwards" — so the destructive/batch cap does not apply; not 4 because validation steps are explicit, not merely implied.

5 / 5

Progressive Disclosure

The skill is self-contained with no bundle files and is organized into well-signaled numbered sections plus a Heuristics preamble and a Recommend decision section, making navigation easy with no nested references; not below 5 because the structure is clean and the cross-skill pointer to `reddit-fetch` is appropriately one level deep.

5 / 5

Total

19

/

20

Passed

Description

82%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, well-targeted description that cleanly answers both what it does and when to use it with natural trigger phrases. The only soft spot is specificity, which states one core recommending action rather than enumerating several concrete capabilities.

DimensionReasoningScore

Specificity

The description names the domain (Claude Code versions) and one core action framed two ways — "Recommend which Claude Code version to run, or whether to update" — matching the anchor for 1-2 concrete actions but not a list of several; it is not score 4 because it does not enumerate multiple specific actions.

3 / 5

Completeness

It explicitly answers both what ("Recommend which Claude Code version to run, or whether to update") and when ("Use when asked which Claude Code version is best/safe..."), with concrete trigger phrases matching the top anchor exactly; not below 5 because neither what nor when is missing or weak.

5 / 5

Trigger Term Quality

It includes natural phrases a user would actually say — "which Claude Code version is best/safe", "whether to update now", "whether a recent release is buggy", "what changed since the installed version" — giving good keyword coverage; not 5 because there are no synonyms/file-extension-style variants to make it comprehensive.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche — Claude Code version selection/update decisions — with distinct triggers and minimal overlap with other skills; not below 5 because the trigger language is specific enough to avoid firing for unrelated skills.

5 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ykdojo/claude-code-tips
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.