This tool manages project environments, dependencies, and script execution while using inline metadata to ensure reproducibility.
Install
mkdir -p .claude/skills/uv && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/1188" && unzip -o skill.zip -d .claude/skills/uv && rm skill.zipInstalls to .claude/skills/uv
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use `uv` instead of pip/python/venv. Run scripts with `uv run script.py`, add deps with `uv add`, use inline script metadata for standalone scripts.Key capabilities
- →Execute Python scripts with ad-hoc dependencies
- →Add project dependencies
- →Initialize projects with inline script metadata
- →Verify script syntax without generating cache files
- →Build pure Python packages using uv_build
How it works
The tool replaces standard pip and venv workflows by managing environments and dependencies directly through CLI commands or inline metadata headers within scripts.
Inputs & outputs
When to use uv
- →Run a single Python script with specific dependencies
- →Add a new package to a project environment
- →Initialize a project with a standalone script
About this skill
Quick Reference
uv run script.py # Run a script
uv run --with requests script.py # Run with ad-hoc dependency
uv run python -m ast foo.py >/dev/null # Verify syntax without writing __pycache__
uv add requests # Add dependency to project
uv init --script foo.py # Create script with inline metadata
Inline Script Dependencies
# /// script
# requires-python = ">=3.12"
# dependencies = ["requests"]
# ///
See scripts.md for full details on running scripts, locking, and reproducibility.
Build Backend
Use uv_build for pure Python packages:
[build-system]
requires = ["uv_build>=0.9.28,<0.10.0"]
build-backend = "uv_build"
See build.md for project structure, namespaces, and file inclusion.
When not to use it
- →When working with non-Python projects
- →When manual virtual environment management is strictly required by legacy tooling
Limitations
- →Requires Python 3.12 or newer for certain inline metadata features
How it compares
It eliminates the need for manual virtual environment creation and activation by handling dependency resolution and execution context automatically.
Compared to similar skills
uv side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| uv (this skill) | 3 | 5mo | Review | Beginner |
| machine-learning-ops-ml-pipeline | 4 | 4mo | No flags | Advanced |
| vastai-core-workflow-b | 1 | 27d | Review | Advanced |
| mflux-dev-env | 2 | 5mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by mitsuhiko
View all by mitsuhiko →You might also like
machine-learning-ops-ml-pipeline
sickn33
Design and implement a complete ML pipeline for: $ARGUMENTS
vastai-core-workflow-b
jeremylongshore
Execute Vast.ai secondary workflow: Core Workflow B. Use when implementing secondary use case, or complementing primary workflow. Trigger with phrases like "vastai secondary workflow", "secondary task with vastai".
mflux-dev-env
filipstrand
Set up and work in the mflux dev environment (arm64 expectation, uv, Makefile targets, lint/format/test).
hugging-face-jobs
patchy631
This skill should be used when users want to run any workload on Hugging Face Jobs infrastructure. Covers UV scripts, Docker-based jobs, hardware selection, cost estimation, authentication with tokens, secrets management, timeout configuration, and result persistence. Designed for general-purpose compute workloads including data processing, inference, experiments, batch jobs, and any Python-based tasks. Should be invoked for tasks involving cloud compute, GPU workloads, or when users mention running jobs on Hugging Face infrastructure without local setup.
mlops-initialization
fmind
Guide to initialize a new MLOps project with standard tools (uv, git, VS Code) and best practices.
mqtt-uns-feeder
clemensv
Use when adding MQTT/Unified-Namespace transport to a feeder in this repo — either alongside an existing Kafka feeder (transport split) or for a brand-new source where MQTT is the primary fit. Covers UNS topic-tree design, xRegistry MQTT messagegroup pattern, paho-mqtt v5 binary-mode CloudEvent emis