CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

veomni-uv-update

Use this skill when updating dependencies managed by uv: bumping a package version, upgrading the uv tool itself, updating torch/CUDA stack, switching transformers version, or regenerating the lockfile. Trigger: 'update dependency', 'bump version', 'upgrade uv', 'update torch', 'update lockfile', 'uv sync fails'.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 excellent operational skill: every scenario is a numbered, executable workflow with exact file paths, grep commands for batch-safe enumeration, explicit validation (tests, lockfile diff review), and error-recovery guidance, all resting on non-obvious repo-specific knowledge. Its only real weakness is that the bulk of the detail — especially the Scenario 3 attention-kernel matrix — is inlined rather than split into reference files, and a few asides could be trimmed.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence throughout — no explanation of what uv, lockfiles, or extras are — and nearly every line carries non-obvious repo-specific facts ("required-version is a range", "there is no generator", "uv venvs are not seeded"). A few flavor asides ("a debugging trap, not a feature") and the long attention-kernel taxonomy could be tightened slightly, matching 'efficient; minor instances of over-explanation' rather than the lean top anchor.

4 / 5

Actionability

Guidance is fully executable: copy-paste commands ("uv lock; uv sync --extra gpu --dev", "grep -rnE \"torch(-npu)?==\" docker/\"), exact pyproject.toml section paths ([tool.uv.sources], [dependency-groups] transformers-stable), specific workflow and Dockerfile paths, and upstream wheel URLs cover the common cases. The few soft steps ("adjust veomni/ accordingly") are minor relative to the density of concrete commands.

5 / 5

Workflow Clarity

Every scenario has a numbered sequence with explicit validation checkpoints — pytest after each sync, "Verify the lockfile diff is reasonable (git diff uv.lock)", grep-based enumeration before batch Dockerfile edits — plus error-recovery feedback ("If uv lock fails due to version conflicts, check...") and a pitfalls checklist, matching the top anchor including its feedback-loop requirement for batch operations.

5 / 5

Progressive Disclosure

The body is organized into clearly headed scenarios with a well-signaled, one-level-deep external reference up front ("Read .agents/knowledge/uv.md for the full dependency architecture"), and no bundle files exist to split into. However, nearly all detail lives inline — the attention-kernel/dependency-metadata taxonomy in Scenario 3 is lengthy enough that it could arguably be a separate reference file — so structure is 'good with minor organization gaps' rather than an overview-plus-references split.

4 / 5

Total

18

/

20

Passed

Description

88%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 strong description: it names the domain (uv-managed dependencies), enumerates five concrete capabilities, and provides an explicit use-when clause with a dedicated trigger list including a failure-mode trigger. The only weakness is a handful of missing natural synonyms that leaves trigger coverage slightly short of comprehensive.

DimensionReasoningScore

Specificity

The description lists five concrete actions — "bumping a package version, upgrading the uv tool itself, updating torch/CUDA stack, switching transformers version, or regenerating the lockfile" — giving comprehensive coverage of the skill's update scenarios, matching the top anchor rather than the 'minor gaps' level below.

5 / 5

Completeness

It explicitly answers 'when' ("Use this skill when updating dependencies managed by uv" plus a dedicated "Trigger:" clause with concrete phrases) and 'what' (the enumerated action list), matching the anchor for clearly and explicitly answering both.

5 / 5

Trigger Term Quality

Triggers include natural phrases users would say ("update dependency", "bump version", "upgrade uv", "update torch", "update lockfile") plus a failure-mode trigger ("uv sync fails"), but common variations like "upgrade transformers", "uv add", or wheel/flash-attn terms are missing, placing it just below the comprehensive synonym coverage of the top anchor.

4 / 5

Distinctiveness Conflict Risk

Triggers like "upgrade uv" and "uv sync fails" are distinct to this niche, but the broad "update dependency" / "bump version" triggers could overlap a generic dependency-management skill, matching 'mostly distinct; minor overlap risk'.

4 / 5

Total

18

/

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

ByteDance-Seed/VeOmni

Path

.agents/skills/veomni-uv-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.