update

Check for updates and upgrade Ouroboros to the latest version

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/update/SKILL.md

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.

The content is a strong, executable runbook: concrete commands, explicit decision logic, and robust fail-closed validation for a mutating operation. Only minor conciseness tightening is warranted.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and assumes Claude's competence without explaining basic concepts, though a few lengthy explanatory sentences in the legacy and breadcrumb sections could be trimmed.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands covering the common update flow plus edge cases, with explicit branch actions for each outcome.	5 / 5
Workflow Clarity	The numbered sequence has explicit decision branches and strong fail-closed validation checkpoints for a mutating operation, including clear "do not" guardrails for the legacy path.	5 / 5
Progressive Disclosure	A single well-organized SKILL.md with clear sections (Usage, Instructions, Safety contract, Footer) and no nested references; structure is easy to navigate for a self-contained skill.	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 is clear and tool-specific but generic: it states the core action without trigger phrases or broader capability coverage. Adding a "Use when..." clause with natural keywords would lift completeness and trigger quality.

Suggestions

Add an explicit "Use when the user wants to update or upgrade Ouroboros" clause to the description to satisfy the 'when' half of completeness.

Include natural trigger keywords (e.g., "update Ouroboros", "upgrade Ouroboros", "ooo update") directly in the description rather than only in the body.

Broaden the action list slightly (e.g., mention runtime/refresh handling) to push specificity from 1-2 actions toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Ouroboros) and two concrete actions ("Check for updates" and "upgrade") but offers no broader coverage of supporting actions like runtime refresh or legacy-install handling.	3 / 5
Completeness	It has a clear "what" (check for updates and upgrade) but no "Use when..." or equivalent trigger guidance, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	The description contains relevant domain words but no natural user trigger phrases with synonyms; the actual trigger keywords live in the body, not the description field.	3 / 5
Distinctiveness Conflict Risk	It is bound to a specific named tool and sub-command with low overlap risk, though narrow trigger phrasing keeps it just below a fully distinct niche.	4 / 5
	Total	13 / 20 Passed

Validation

100%

Warnings & errors only

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: Q00/ouroboros
Path: skills/update/SKILL.md
Commit: 80333ae

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.