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.

76

Quality

95%

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplar content body: lean yet packed with novel domain heuristics, fully executable commands, a clearly sequenced workflow with validation checkpoints, and clean single-file organization. No dimension shows a meaningful weakness.

DimensionReasoningScore

Conciseness

The body is dense and information-rich, assumes Claude's competence (no padding explaining what npm/CHANGELOG/Reddit are), and its prose encodes genuinely non-obvious domain heuristics (stable≠LTS, Reddit hard-blocks, the DuckDuckGo-hop unlock) rather than concepts Claude already knows.

3 / 3

Actionability

It provides concrete, executable commands throughout (claude --version, npm view dist-tags, gh api search/issues, claude -p ... --output-format json, claude install X.Y.Z), with required substitutions (<LATEST>, <DATE>, <model-id>) clearly flagged rather than left as pseudocode.

3 / 3

Workflow Clarity

A clearly numbered 1–5 sequence (installed vs published → changelog gap → community sentiment → test the claim → recommend) with explicit validation checkpoints such as confirming with "claude --version" after install and re-running the model command after updating.

3 / 3

Progressive Disclosure

A single self-contained file with well-organized, numbered sections and no nested references; the only external pointer is a one-level cross-skill reference to reddit-fetch. No bundle files exist, so there is nothing to over- or under-split.

3 / 3

Total

12

/

12

Passed

Description

90%

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 well-constructed description with explicit trigger guidance, natural user phrasings, and a clear distinct niche. Its only weakness is that the stated capability is a single recommendation action rather than a list of multiple concrete actions.

Suggestions

Consider naming the concrete outputs/actions the skill produces alongside the recommendation (e.g. "...pin or roll back to a specific version, or disable the auto-updater") to lift specificity toward the anchor-3 bar.

DimensionReasoningScore

Specificity

The description names the recommendation action ("Recommend which Claude Code version to run, or whether to update") but this is essentially a single decision action with two facets, not the multiple distinct concrete actions (e.g. extract/fill/merge) that the anchor-3 example lists.

2 / 3

Completeness

It explicitly answers both what (recommend a version or update decision) and when (an explicit "Use when asked..." trigger), matching the anchor-3 example.

3 / 3

Trigger Term Quality

The "Use when..." clause gives natural phrasings 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 coverage.

3 / 3

Distinctiveness Conflict Risk

It occupies a clear niche (Claude Code version selection) with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

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.