CtrlK
BlogDocsLog inGet started
Tessl Logo

uv-package-manager

Master the uv package manager for fast Python dependency management, virtual environments, and modern Python project workflows. Use when setting up Python projects, managing dependencies, or optimizing Python development workflows with uv.

65

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/python-development/skills/uv-package-manager/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 highly actionable with executable command patterns and clean progressive disclosure into one reference file. Its main weaknesses are conceptual padding that assumes too little of Claude and the absence of validation checkpoints around dependency-mutation workflows.

Suggestions

Cut the 'What is uv?', 'Key Features', and 'UV vs Traditional Tools' sections (and the duplicate 'uv add --upgrade requests' line) to remove concepts Claude already knows.

Add verification checkpoints after batch/destructive dependency operations, e.g. run 'uv sync' then 'uv tree --outdated' or 'uv lock --check' to confirm the resulting state.

DimensionReasoningScore

Conciseness

Command patterns are mostly efficient, but sections like 'What is uv?', 'Key Features', and 'UV vs Traditional Tools' re-explain concepts Claude already knows, and Pattern 6 repeats 'uv add --upgrade requests' twice, leaving noticeable padding that could be trimmed.

3 / 5

Actionability

Every section provides concrete, copy-paste-ready commands covering common cases (init, add, remove, upgrade, lock, python install, venv, run), with specific flags and syntax throughout.

5 / 5

Workflow Clarity

Patterns are clearly grouped by task, but batch/destructive dependency mutations (uv add, uv sync --upgrade, uv remove, uv lock --upgrade) lack validation or verification checkpoints (e.g. 'uv sync' after, 'uv tree --outdated' to confirm), which per the rubric caps this dimension at 3.

3 / 5

Progressive Disclosure

SKILL.md is a concise overview organized into clear sections, with a single one-level-deep reference (references/advanced-patterns.md) clearly signaled and linked at the end; the referenced file exists and is appropriately separated.

5 / 5

Total

16

/

20

Passed

Description

83%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 strong: it pairs a concrete capability statement with an explicit 'Use when...' trigger clause and is clearly scoped to uv. Minor gains are available by adding natural synonyms and format/file-extension terms.

Suggestions

Add natural synonyms and concrete artifacts (e.g. 'lockfiles', 'pyproject.toml', '.venv') to broaden trigger-term coverage.

Tighten the capability list toward the most distinctive uv actions (e.g. 'install Python interpreters', 'resolve and lock dependencies') to lift specificity.

DimensionReasoningScore

Specificity

Names the domain and several concrete capabilities ('fast Python dependency management, virtual environments, and modern Python project workflows'); lists multiple specific actions but is not exhaustive, so it sits just below the comprehensive-coverage anchor.

4 / 5

Completeness

Clearly answers 'what' ('dependency management, virtual environments, and modern Python project workflows') and explicitly answers 'when' with the concrete 'Use when setting up Python projects, managing dependencies, or optimizing Python development workflows with uv' trigger clause.

5 / 5

Trigger Term Quality

Natural phrases like 'setting up Python projects', 'managing dependencies', and 'virtual environments' are present, but common synonyms and explicit file/format terms (e.g. pyproject.toml, lockfile) are missing.

4 / 5

Distinctiveness Conflict Risk

The repeated 'with uv' qualifier carves a clear niche distinct from generic pip/poetry skills, with only minor overlap risk against broad Python packaging skills.

4 / 5

Total

17

/

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
wshobson/agents
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.