About uv-package-manager
A practical guide skill for using uv to manage Python projects, dependencies, interpreters, environments, and lockfiles. It covers workflows such as migration, monorepos, CI/CD, and Docker builds, with guidance to inspect project hooks and use isolated environments.
Key features
- 01Python dependency management
- 02Virtual environment and interpreter setup
- 03Lockfile-based reproducible workflows
- 04Migration from other package tools
- 05Monorepo and build guidance
Use cases
- 01Starting a Python project
- 02Migrating from pip or Poetry
- 03Checking locked dependencies in CI
- 04Managing Python dependencies in Docker
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/uv-package-managerin Claude Code to confirm it loaded.
Bundled filesresources/implementation-playbook.md
Details
From the project READMEUV 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.
Use this skill when
- Setting up new Python projects quickly
- Managing Python dependencies faster than pip
- Creating and managing virtual environments
- Installing Python interpreters
- Resolving dependency conflicts efficiently
- Migrating from pip/pip-tools/poetry
- Speeding up CI/CD pipelines
- Managing monorepo Python projects
- Working with lockfiles for reproducible builds
- Optimizing Docker builds with Python dependencies
Do not use this skill when
- The task is unrelated to uv package manager
- You need a different domain or tool outside this scope
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
- If detailed examples are required, open
resources/implementation-playbook.md.
Example
# Existing reviewed project: verify the lock before syncing.
uv lock --check
uv sync --locked
uv run --locked pytest
Inspect project build hooks/dependencies before installation or running code. Use an isolated environment and explicit authorization for downloads, installs and hook/config changes.
Resources
resources/implementation-playbook.mdfor detailed patterns and examples.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.