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.

Quality

66%

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 ./skills/uv-package-manager/SKILL.md

Quality

Content

65%

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

The body is a highly actionable, executable command reference for uv, but it suffers from verbosity and redundancy across repeated comparison and best-practices sections, lacks validation checkpoints in its workflows, and is monolithic with no progressive disclosure to bundle files.

Suggestions

Collapse the three overlapping comparison sections and the duplicate 'Best Practices' / 'Best Practices Summary' lists into one authoritative section to remove redundancy.

Add explicit validation/verification steps to risky or batch workflows (e.g. 'uv lock --check' after uv lock, 'uv sync --frozen' verification in CI/Docker) to earn workflow-clarity credit.

Move the full Dockerfile, CI, pyproject.toml, and command-reference blocks into referenced files (e.g. references/docker.md, references/ci-cd.md) so SKILL.md stays a concise overview with one-level-deep pointers.

Dimension	Reasoning	Score
Conciseness	The per-block command examples are lean, but the ~800-line body includes conceptual filler ('What is uv?', 'Key Features') and substantial redundancy (three comparison sections and two overlapping Best Practices sections) that could be tightened.	2 / 3
Actionability	Abundant copy-paste-ready, executable commands and complete config files (pyproject.toml, GitHub Actions YAML, Dockerfile, pre-commit config) provide concrete, specific guidance throughout.	3 / 3
Workflow Clarity	Multi-step workflows (new project, CI/CD, Docker, migration) are clearly sequenced, but validation checkpoints and feedback loops are missing for batch/destructive operations like uv sync, uv lock, and Docker builds.	2 / 3
Progressive Disclosure	Sections are well-organized, but the skill is a single monolithic ~800-line file with no bundle references; detailed configs and the command reference that could be split out remain inline.	2 / 3
	Total	9 / 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 cleanly answers what the skill does and when to use it with an explicit trigger clause, but its capability list relies on area nouns rather than concrete actions and its trigger terms miss common variations like pip, venv, and lockfile.

Suggestions

Replace area nouns with concrete actions, e.g. 'add and remove dependencies, create virtual environments, pin Python versions, and manage lockfiles'.

Add common trigger variations users would actually say, such as 'pip', 'venv', 'install packages', or 'lockfile'.

Tighten the trigger to uv-specific contexts (e.g. 'when the user wants faster pip-compatible dependency management or mentions uv') to reduce overlap with pip/poetry skills.

Dimension	Reasoning	Score
Specificity	Names the domain and several specific areas ('fast Python dependency management, virtual environments, and modern Python project workflows') but uses noun-phrases rather than concrete action verbs, falling short of the anchor-3 pattern of listing multiple concrete actions.	2 / 3
Completeness	Explicitly answers both 'what' (master uv for dependency management, venvs, project workflows) and 'when' via a clear 'Use when...' trigger clause, matching the anchor-3 example.	3 / 3
Trigger Term Quality	The 'Use when setting up Python projects, managing dependencies, or optimizing Python development workflows' clause includes natural terms a user might say, but omits common variations like 'pip', 'venv', 'install packages', and 'lockfile'.	2 / 3
Distinctiveness Conflict Risk	'uv' is a clearly named niche, but the generic 'setting up Python projects, managing dependencies' triggers could overlap with pip or poetry skills, so it is somewhat specific rather than clearly non-conflicting.	2 / 3
	Total	9 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (833 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: Galaxy-Dawn/claude-scholar
Path: skills/uv-package-manager/SKILL.md
Commit: 2f7766f

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