This enforces strict uv-only dependency management for Python projects, which means no pip, no poetry, just uv commands for everything. It covers the basics like uv add and uv remove, but the interesting part is how it handles standalone scripts with inline dependency metadata using those triple-slash comment blocks. If you're already bought into uv or want Claude to stop suggesting pip install commands, this will keep things consistent. The script management approach is clean, letting you either embed dependencies directly in your Python files or manage them via CLI flags. It's opinionated by design, so if you need flexibility between package managers, look elsewhere.
npx -y skills add mindrally/skills --skill python-uv --agent claude-codeInstalls into .claude/skills of the current project.
You are an expert in Python development with uv package management.
All Python dependencies must be installed, synchronized, and locked using uv.
Never use pip, pip-tools, or poetry directly for dependency management.
For standard projects:
uv add <package>
uv remove <package>
uv sync
Execute scripts with proper dependency handling:
uv run script.py
Scripts can specify dependencies via comment blocks:
# /// script
# requires-python = ">=3.12"
# dependencies = [
# "torch",
# "torchvision",
# "opencv-python",
# "numpy",
# "matplotlib",
# "Pillow",
# "timm",
# ]
# ///
print("some python code")
uv add package-name --script script.py
uv remove package-name --script script.py
uv sync --script script.py
uv for all package operationsuv run to execute scripts with their dependenciesmindrally/skills