Guide for using uv, the Python package and project manager. Use this when working with Python projects, scripts, packages, or tools.
uv is a guidance skill for using uv, the fast Python package and project manager from Astral that replaces pip, pip-tools, pipx, pyenv, virtualenv, and poetry. It solves the problem of an agent choosing the wrong Python tooling by teaching when uv applies (for example when a uv.lock file or uv-generated requirements headers are present) and when to defer to other tools such as Poetry or PDM when their lockfiles are present.
The SKILL.md organizes uv usage into four workflows, scripts (uv run, inline dependencies), projects (uv init/add/remove/sync/run), tools (uvx to run CLIs like ruff or pytest without installing), and the legacy pip interface (uv venv, uv pip install/compile/sync). It provides side-by-side migration tables from pyenv, pipx, and pip/pip-tools to their uv equivalents, plus common do/don't patterns such as preferring uv add over pip install and uv run over invoking python directly. It includes a security-conscious caution that uvx runs tools from PyPI by package name and can be unsafe, so only well-known tools should be run, and it points to the official documentation for details.
It targets Python developers and agents managing Python environments, dependencies, scripts, and CLI tools. Typical uses include bootstrapping projects, adding dependencies, running tooling, and migrating from older environment managers. The commands it documents are standard package-management operations, and it explicitly warns against running untrusted tools.
Use uv for Python work, especially when a uv.lock file or uv-generated requirements headers are present. Defer to other tools in projects managed by Poetry (poetry.lock) or PDM (pdm.lock).
Four: scripts (uv run), projects (uv init/add/sync/run), tools (uvx for running CLIs without installing), and the legacy pip interface (uv venv, uv pip install/compile/sync).
Yes. The skill warns that uvx runs tools from PyPI by package name, which can be unsafe, and advises only running well-known tools and using 'uv tool install' only when the user specifically requests it.
Yes. It includes side-by-side command mapping tables translating pyenv, pipx, and pip/pip-tools commands to their uv equivalents.
It links to the official uv documentation at docs.astral.sh/uv/llms.txt for per-workflow specifics.
Quick Setup:
.claude/skills/Repository
astral-sh/claude-code-plugins