2.6k
GitHub Stars
3
Bundled Files
6 months ago
Catalog Refreshed
8 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill uv-global- _meta.json625 B
- install.sh1.7 KB
- SKILL.md2.0 KB
Overview
This skill provisions and reuses a single global uv environment at ~/.uv-global so you can install Python dependencies for quick, ad hoc scripts without polluting the system interpreter. It creates a shared virtual environment and handy shims for fast, repeatable runs. Use it to speed up lightweight scripting workflows where a full project venv would be overkill.
How this skill works
The installer ensures the uv tool is present (via brew or the official curl installer), creates a global uv project directory at ~/.uv-global, and builds a virtual environment in ~/.uv-global/.venv with common packages and shims. You then add packages into that environment with uv --project ~/.uv-global add and run scripts with uv --project ~/.uv-global run, keeping your system Python clean.
When to use it
- You need one-off or short-lived Python scripts that require extra packages (scraping, data munging, quick automation).
- You want a persistent shared environment across ad hoc tasks without creating per-project venvs.
- You prefer not to modify system Python or global site-packages directly.
- You need fast setup for experiments or demos where managing a separate project is unnecessary.
Best practices
- Install uv first using brew or the official curl installer if missing, then run the provided install script.
- Add required packages with uv --project ~/.uv-global add rather than pip in the system interpreter.
- Keep scripts anywhere and always use --project ~/.uv-global when running to ensure they use the global env.
- If a task becomes a long-lived project, migrate to a project-local venv to avoid dependency conflicts.
- Optionally prepend ~/.uv-global/.venv/bin to PATH for convenience, but be explicit with --project in automation.
Example use cases
- Quickly run a web-scraping script that needs requests and beautifulsoup without creating a new venv.
- Process a CSV or JSON file with pandas for one-off analysis on a laptop or server.
- Prototype a small automation that uses third-party libraries, then discard or migrate later.
- Run utility scripts on remote machines where installing project-specific environments is inconvenient.
FAQ
No. The global uv environment lives in ~/.uv-global/.venv, and packages installed there do not modify the system interpreter.
How do I see what packages are installed in the global env?
Run uv --project ~/.uv-global pip list to inspect installed packages in the shared virtual environment.