uv-package-manager

Comprehensive guide to using uv, an extremely fast Python package installer and resolver written in Rust, for modern Python project management and dependency workflows.

Quality

27%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/uv-package-manager/SKILL.md

Quality

Content

18%Scale 1-5

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

This skill is essentially a placeholder with no actionable content. It contains no uv commands, no code examples, no concrete workflows — just generic meta-instructions that could apply to any tool. The sole referenced resource file does not exist in the bundle, leaving the skill entirely hollow.

Suggestions

Add concrete uv commands and code examples directly in the SKILL.md (e.g., `uv init`, `uv add`, `uv sync`, `uv run`) covering the most common workflows mentioned in the trigger list.

Replace the generic Instructions bullets with specific, sequenced workflows for key tasks like project setup, dependency management, and environment creation, including validation steps (e.g., `uv sync --check`).

Either create the referenced `resources/implementation-playbook.md` bundle file with detailed patterns, or inline the essential content directly in the skill body.

Remove the repeated description line and trim the 'Use this skill when' list to only non-obvious triggers that Claude wouldn't infer from context.

Dimension	Reasoning	Score
Conciseness	The 'Use this skill when' and 'Do not use this skill when' sections are padded with obvious trigger conditions that Claude can infer. The description is repeated from the frontmatter. However, the instructions section itself is brief. Overall, there's noticeable filler without being severely verbose.	3 / 5
Actionability	The skill provides zero concrete code, commands, or executable guidance. Instructions like 'Clarify goals, constraints, and required inputs' and 'Apply relevant best practices' are entirely vague and abstract. There are no uv commands, no code examples, no specific steps — everything is deferred to a resource file that doesn't exist in the bundle.	1 / 5
Workflow Clarity	There is no meaningful workflow defined. The four bullet points in Instructions are generic platitudes ('Clarify goals', 'Apply best practices', 'Validate outcomes') with no sequencing, no specific steps, and no validation checkpoints relevant to uv operations.	1 / 5
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed content, which is a reasonable disclosure pattern, but the bundle confirms no such file exists. The SKILL.md itself contains almost no substantive content to serve as an overview, making it an empty shell pointing to a nonexistent resource.	2 / 5
	Total	7 / 20 Passed

Description

36%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 identifies the tool (uv) and its general domain (Python package management) but lacks concrete actions, explicit trigger guidance, and natural user phrases. It reads more like a document title than a skill description, relying on vague terms like 'comprehensive guide' and 'workflows' rather than specifying what the skill actually enables Claude to do.

Suggestions

Add a 'Use when...' clause with trigger terms like 'uv install', 'uv pip', 'Python dependencies', 'pyproject.toml', 'virtual environment with uv', or when users mention 'uv' by name.

Replace vague phrases like 'project management and dependency workflows' with concrete actions such as 'install packages, resolve dependencies, manage virtual environments, create lockfiles, publish packages'.

Include synonyms and related terms users might naturally say, such as 'pip alternative', 'fast package installer', 'uv sync', 'uv run', '.venv' to improve trigger term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain (Python package management with uv) but actions are minimal and generic — 'project management and dependency workflows' is vague. No concrete actions like 'install packages', 'resolve dependencies', 'create virtual environments', or 'manage lockfiles' are listed.	2 / 5
Completeness	Has a vague 'what' (guide to using uv for project management and dependency workflows) but completely lacks a 'when' clause. There is no explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when...' caps completeness at 3, and the 'what' is also weak.	2 / 5
Trigger Term Quality	Includes relevant keywords like 'uv', 'Python', 'package installer', 'resolver', 'dependency', and 'project management', but misses natural user phrases like 'pip alternative', 'virtual environment', 'venv', 'pyproject.toml', 'lockfile', or common commands users would ask about.	3 / 5
Distinctiveness Conflict Risk	Mentioning 'uv' specifically helps distinguish it from generic Python packaging skills, but 'Python project management and dependency workflows' is broad enough to overlap with skills about pip, poetry, conda, or general Python development.	3 / 5
	Total	10 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/uv-package-manager/SKILL.md
Commit: 900c504

Reviewed: 5 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.