update

Check for updates and upgrade Ouroboros to the latest version

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

77%

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

The body is highly actionable with a clear, validated update workflow, but it leans verbose in places (duplicated version-check snippets, a tangential breadcrumb section) and keeps all detail inline rather than offloading any to reference files.

Suggestions

Consolidate the duplicate pre-release and stable PyPI snippets into one snippet with conditional version selection to remove the repeated boilerplate.

Consider moving the per-installer (uv/pipx/pip) upgrade commands into a short reference file or collapsing the three branches into a table, reducing the inline command wall.

Trim or relocate the RFC #1392 breadcrumb footer section so the core update procedure stays lean; it adds non-procedural overhead to a primarily action-oriented skill.

Dimension	Reasoning	Score
Conciseness	The body is action-dense and assumes Claude's competence, but the near-duplicate pre-release vs stable PyPI snippets and the tangential RFC #1392 breadcrumb footer could be tightened, fitting the mostly-efficient-but-could-be-tightened anchor.	2 / 3
Actionability	Provides fully executable bash and Python commands for version detection, per-installer (uv/pipx/pip) upgrades, runtime integration, and the CLAUDE.md marker update, matching the copy-paste-ready anchor.	3 / 3
Workflow Clarity	A clearly sequenced five-step process with an explicit confirmation checkpoint (AskUserQuestion in step 3) and a verification checkpoint (version check in step 4d) plus fallback paths, matching the clear-sequence-with-validation anchor.	3 / 3
Progressive Disclosure	Sections are well organized but the skill is monolithic at roughly 190 lines with no external reference files, so per-method install detail and the breadcrumb footer are inline rather than split out, fitting the structure-present-but-should-be-separate anchor.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 specific and distinctive thanks to the named product and concrete actions, but it omits explicit trigger guidance, leaving the 'when to use' question only implied and capping completeness and trigger-term coverage.

Suggestions

Add a 'Use when...' clause naming trigger phrases, e.g. 'Use when the user asks to update or upgrade Ouroboros, or mentions checking for a newer Ouroboros version.'

Broaden trigger terms in the description to include common variations like 'update Ouroboros', 'upgrade Ouroboros', and 'ooo update'.

Keep the third-person voice (currently correct) while folding in the when-to-use context to lift completeness from 2 to 3.

Dimension	Reasoning	Score
Specificity	Names concrete actions ("Check for updates", "upgrade ... to the latest version") tied to a specific product, matching the multiple-specific-actions anchor rather than the vague single-action anchor at 2.	3 / 3
Completeness	Clearly answers what the skill does but provides no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	Includes natural terms ("updates", "upgrade", "Ouroboros", "latest version") but offers only the core pair with no common variations or trigger phrasing in the description itself, fitting the some-keywords-but-missing-variations anchor.	2 / 3
Distinctiveness Conflict Risk	The named product "Ouroboros" creates a clear niche with a distinct trigger ("update Ouroboros") that is unlikely to conflict with other skills, matching the clear-niche anchor.	3 / 3
	Total	10 / 12 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: .claude-plugin/skills/update/SKILL.md
Commit: f09fa36

Reviewed: about 2 hours 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.