uv-global

What This Skill Does

The uv-global skill provides a streamlined mechanism to manage a single, persistent Python virtual environment located at ~/.uv-global. Built upon the high-performance uv package manager, this skill allows users to maintain a lightweight, ready-to-use Python runtime for ad hoc scripts and experimental tasks. By decoupling these temporary dependencies from the system-level Python interpreter, it prevents package conflicts and keeps the user's development environment clean. It is designed for speed, efficiency, and ease of use, ensuring that common tools are available immediately without the overhead of creating and configuring a full project directory every time a quick script needs to be written.

Installation

To integrate this skill, use the clawhub command: clawhub install openclaw/skills/skills/guoqiao/uv-global. Once initiated, the skill executes a dedicated installation script that validates the presence of the uv tool. If uv is not detected on your system, the script automatically bootstraps it via Homebrew or the official curl installer. It then initializes the global project at ~/.uv-global and prepares a virtual environment containing common utility packages. For optimal developer experience, we recommend prepending the path ~/.uv-global/.venv/bin to your environment’s PATH variable, which enables direct invocation of your global Python tools.

Use Cases

This skill is ideal for rapid prototyping, data scraping, or small-scale automation tasks where installing a full-blown development environment is excessive. Use it when you need to quickly run a Python script that requires libraries like pandas, requests, or beautifulsoup4 without wanting to manage a unique pyproject.toml or requirements.txt file for every minor task. It bridges the gap between 'messy system Python' and 'over-engineered project environments.'

Example Prompts

1. "I need to scrape a quick table from a website; can you use the global uv environment to install requests and beautifulsoup, then write the scraping script for me?"
2. "Set up a Python script to parse this JSON file and print the summary; make sure it uses the global uv environment so I don't have to install dependencies manually."
3. "Run this data conversion script using the shared uv environment and let me know if it requires any additional packages."

Tips & Limitations

Maintain a organized approach: the uv-global environment is intended for convenience, not for long-term production development. If you find your script growing in complexity—specifically if you need to share the script with others or if it requires specific, locked versions of dependencies—you should migrate it to a standalone project with its own virtual environment. You can check the state of your global packages at any time using uv --project ~/.uv-global pip list. Always remember that since this is a shared environment, installing a specific version of a package for one script might impact others; for strict dependency management, use project-local environments.