CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ctx-upgrade

Update context-mode to the latest release.

Quality

78%

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/ctx-upgrade/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

93%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 model of lean, actionable instruction for a simple tool-orchestration skill: exact tool names, explicit ordering, presentation guidance, and conditional restart handling in three sentences. The only minor gap is the absence of error-recovery guidance if the upgrade or the doctor check fails.

DimensionReasoningScore

Conciseness

The body is three lean sentences ('Call the ctx_upgrade tool and show its table to the user. Then call ctx_doctor and show its table. If a restart is needed, say so in one sentence.') with zero padding and no explanations of concepts Claude already knows. Not 4 because there is nothing left to trim — every token earns its place.

5 / 5

Actionability

It names the exact tools to call (ctx_upgrade, ctx_doctor), the order ('Then'), how to present output ('show its table'), and how to handle the restart case ('say so in one sentence') — fully executable instruction-only guidance covering the single common case. Not 4 because there are no gaps in the common flow.

5 / 5

Workflow Clarity

Clear two-step sequence ('Call the ctx_upgrade tool... Then call ctx_doctor') with the doctor call acting as an explicit post-upgrade checkpoint plus conditional restart handling. Not 5 because there is no error-recovery guidance if the upgrade fails or ctx_doctor reports problems; not 3 because the sequence and checkpoints are explicit and the operation is neither destructive nor batch.

4 / 5

Progressive Disclosure

This is a one-sentence skill under 50 lines with no bundle files (no references/, scripts/, or assets/ directories exist) and no content that warrants external references, so per the simple-skill guideline it scores 5. Not 4 because there is no organization gap — nothing needs splitting or navigation.

5 / 5

Total

19

/

20

Passed

Description

53%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 states a clear, concrete 'what' but omits any 'when to use this' guidance, and its trigger vocabulary is thin — notably missing 'upgrade', the very word in the skill's name. It is reasonably distinct thanks to the specific tool name, but reads as a bare capability statement rather than a complete trigger description.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to update or upgrade context-mode to a newer version' — the missing 'when' currently caps completeness at 3.

Include the synonym 'upgrade' (the skill is named ctx-upgrade) plus variations like 'new version' or 'check for updates' to broaden natural trigger-term coverage.

Briefly state what the post-upgrade step covers (e.g., 'then verify the installation with ctx_doctor') so the described capabilities are more comprehensive.

DimensionReasoningScore

Specificity

'Update context-mode to the latest release' names the domain ('context-mode') and one concrete action ('update... to the latest release'), matching the 1-2-concrete-actions anchor. Not 2 because the stated action is more informative than a bare generic verb like 'Processes PDF files'; not 4 because only a single action is listed with no breadth of coverage.

3 / 5

Completeness

The 'what' is clear ('Update context-mode to the latest release') but there is no 'Use when...' clause or equivalent trigger guidance anywhere, which per the judging guidelines caps completeness at 3. Not 4 because the 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

It contains 'update', 'context-mode', and 'latest release' — relevant keywords a user of this tool would naturally say — but misses common variations such as 'upgrade' (despite the skill being named ctx-upgrade) or 'new version'. Matches 'some relevant keywords but missing common variations or synonyms'; not 4 because synonym coverage is entirely absent.

3 / 5

Distinctiveness Conflict Risk

It is scoped to a specific tool ('context-mode') and a specific operation (updating to the latest release), making it mostly distinct with only minor overlap risk against closely related context-mode skills (e.g., configuration or diagnostics). Not 5 because it lacks distinct trigger phrases that would fully separate it from those neighbors.

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

mksglu/context-mode

Path

skills/ctx-upgrade/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.