CtrlK
BlogDocsLog inGet started
Tessl Logo

update

Check for updates and upgrade Ouroboros to the latest version

61

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./.claude-plugin/skills/update/SKILL.md

The canonical home for this skill is update in Q00/ouroboros

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 strong, executable instruction skill with concrete commands, explicit fail-closed guardrails, and clean sectioning; its main weaknesses are an implicit post-update verification step and slightly dense inline safety/breadcrumb prose.

DimensionReasoningScore

Conciseness

The body is information-dense and assumes Claude's competence without explaining basic concepts; only the rationale prose in the breadcrumb footer section could be trimmed, fitting the 'efficient with minor over-explanation' anchor.

4 / 5

Actionability

It provides copy-paste-ready commands (`ouroboros update --check`, `--yes`, `--yes --runtime all`, `--help`, `--version`) with explicit decision branches covering the common update cases.

5 / 5

Workflow Clarity

A clearly numbered 1-4 sequence with validation checkpoints (pre-check, fail-closed on errors, --help probe) is present, but post-update success verification is only implicit ('Show the command's result') rather than an explicit validate step.

4 / 5

Progressive Disclosure

Content is well-organized into Usage, Instructions, Safety contract, and breadcrumb sections with no nested or buried references and no external files needed; at ~107 lines it is slightly long for a single file, so it sits at 4 rather than 5.

4 / 5

Total

17

/

20

Passed

Description

61%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 is clear and product-specific with decent natural trigger terms, but it lacks an explicit 'Use when...' clause and only names two actions, leaving it mid-range on completeness and specificity.

Suggestions

Add a 'Use when the user asks to update or upgrade Ouroboros' clause to lift completeness above 3.

Include the CLI trigger 'ooo update' and a couple more concrete actions (e.g., refresh host integrations) to improve specificity and trigger coverage.

Tighten distinctiveness by pairing the product name with the specific install-identity-preserving behavior so it cannot be confused with a generic package-update skill.

DimensionReasoningScore

Specificity

Names the domain (Ouroboros) plus two concrete actions ('Check for updates' and 'upgrade ... to the latest version'), matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

It clearly answers 'what' (check for updates and upgrade) but has no 'Use when...' clause or explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

'updates', 'upgrade Ouroboros', and 'latest version' are natural phrases users would say, with the update/upgrade synonym pair covered; only minor terms like the CLI 'ooo update' form are missing.

4 / 5

Distinctiveness Conflict Risk

Naming the specific product Ouroboros gives it a clear niche with minimal conflict risk, but the action verbs ('update'/'upgrade') are generic enough to leave minor overlap risk, fitting the 4 anchor better than 5.

4 / 5

Total

14

/

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
Q00/ouroboros
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.