Manage Python packages, virtual environments, and dependencies using uv. Use when installing packages, creating virtual environments, initializing Python projects, resolving dependencies, or running Python scripts.
95
93%
Does it follow best practices?
Impact
98%
1.84xAverage score across 3 eval scenarios
Passed
No known issues
This workspace exclusively uses uv for Python package management, dependency resolution, and virtual environment handling. Never fall back to pip or python -m venv unless uv explicitly fails.
pip installuv add <package> (for pyproject.toml-managed projects) or uv pip install <package> (for ad-hoc installs)python -m venvuv venv to create virtual environmentsuv pip compile to generate lockfiles (requirements.txt or uv.lock) instead of pip freezeuv init when initializing a new Python projectuv is available; do not fall back to pip unless uv explicitly fails| Task | Command |
|---|---|
| Install / add a package | uv add <package> |
| Ad-hoc install (no pyproject.toml) | uv pip install <package> |
| Run a script | uv run <script.py> |
| Sync environment to lockfile | uv sync |
| Install a dev tool | uv tool install <tool> |
| Create a virtual environment | uv venv |
| Compile a lockfile | uv pip compile requirements.in -o requirements.txt |
| Initialize a new project | uv init |
# Good
uv add requests
# Bad — never do this
pip install requests# Good
uv venv .venv
# Bad — never do this
python -m venv .venvuv run main.pyuv syncc0b2e4b
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.