CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

update

Check for updates and upgrade Ouroboros to the latest version

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%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.

An exemplar instruction-only skill: concise, fully executable, with a check-first workflow containing explicit failure branches and a fail-closed legacy path, all within a well-organized single file. No bundle files exist, yet nothing in the body references any, so disclosure is appropriately flat.

DimensionReasoningScore

Conciseness

The body is imperative and dense throughout ("Run `ouroboros update --check`", "Never substitute a manual upgrade, and never infer ownership from `uv tool list`, `pipx list`, PATH order, directory names, or the active agent runtime") with zero padding or explanation of concepts Claude already knows. Every token carries skill-specific direction; matches the anchor 5 example of lean, competence-assuming content.

5 / 5

Actionability

Every branch is fully executable with concrete commands: `ouroboros update --check`, `ouroboros update --yes`, `ouroboros update --yes --runtime all`, `ouroboros --version`, `ouroboros_session_status`, `/reload-plugins`, and `ooo setup`, covering up-to-date, update-available, check-failed, and legacy-install cases. This is copy-paste-ready guidance with specific examples for the common cases, matching anchor 5.

5 / 5

Workflow Clarity

A clear 4-step sequence with explicit validation checkpoints: check-first before any change, defined error-recovery branches (check fails but help works → report native error and stop; help broken → fail-closed legacy path allowing only a read-only `--version`), and post-update verification by relaying the command's result. The explicit validate-then-act-with-fallback structure matches anchor 5; it is not anchor 4 because no meaningful checkpoints are missing.

5 / 5

Progressive Disclosure

The skill is under 50 lines, self-contained, and needs no external references; sections are well-organized (command block, Instructions, footer spec) with extra options delegated to `ouroboros update --help` rather than inlined. Per the rubric's simple-skill exception, this scores 5.

5 / 5

Total

20

/

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.

A concise, correctly-scoped description that clearly states what the skill does but provides no explicit trigger guidance and only a thin set of natural keywords. The specific tool name keeps conflict risk low, while the missing "Use when" clause and absent synonyms are the main weaknesses.

Suggestions

Add a trigger clause, e.g. "Use when the user asks to update or upgrade Ouroboros, check its version, or bring an Ouroboros install up to date."

Include natural trigger variants users would actually say — "update Ouroboros", "up-to-date", "version check" — rather than only "check for updates" and "latest version".

Broaden the stated actions to reflect what the skill actually handles, such as refreshing Claude Code and Codex host integrations and reporting version mismatches, so the description matches the body's coverage.

DimensionReasoningScore

Specificity

"Check for updates and upgrade Ouroboros to the latest version" names the domain plus two concrete actions, matching anchor 3 ("Names domain and 1-2 concrete actions, but not comprehensive"). It is not 4 because it omits real capabilities the body covers (host-integration refresh, restart guidance, legacy-install handling).

3 / 5

Completeness

The "what" is clear (check for updates, upgrade to latest), but there is no "Use when..." clause or equivalent trigger guidance, which the rubric explicitly caps at 3. It is not 2 because the "what" half is concrete rather than vague.

3 / 5

Trigger Term Quality

Natural phrases like "check for updates", "upgrade", and "latest version" are present, but the keyword surface is a single short sentence missing common variations such as "up-to-date", "version check", or "update Ouroboros". This sits at anchor 3 (some relevant keywords, missing common variations) rather than 4's good-but-incomplete coverage.

3 / 5

Distinctiveness Conflict Risk

Naming "Ouroboros" gives a mostly distinct niche with only minor overlap risk against other tool-update skills triggered by generic phrases like "check for updates" or "latest version", matching anchor 4. It is not 5 because those generic update phrases alone would not unambiguously select this skill.

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

Q00/ouroboros

Path

skills/update/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.