Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Prioritize uv over pip for all Python package management and execution. When running ANY Python command or CLI tool (python, dbt, pytest, etc.), MUST wrap wi...
Prioritize uv over pip for all Python package management and execution. When running ANY Python command or CLI tool (python, dbt, pytest, etc.), MUST wrap wi...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
This is a mandatory skill for all Python-related tasks. When the user mentions Python, dbt, or ANY Python package, you MUST: NEVER run Python commands directly (python, python3, dbt, pytest, etc.) ALWAYS wrap them with uv run or uvx NEVER install packages with pip install ALWAYS use uv add or uv pip install
CommandWhen to UseExampleuv run <tool>Ferramenta do projeto - precisa importar seus módulos, usada regularmenteuv run pytest tests/uvx <tool>Utilitário externo - usa Python como runtime, mas não é parte do seu appuvx ruff check .
Preciso rodar uma ferramenta Python? ├─ A ferramenta precisa importar meus módulos do projeto? │ └─ SIM → uv run <comando> └─ A ferramenta só analisa/transforma código externo? └─ SIM → uvx <comando>
uvx creates a temporary, isolated environment. Use it for tools that: Analyze code without importing project modules (linters, formatters, type checkers) Are one-off utilities not tied to your project Shouldn't pollute your project's dependencies uvx ruff check . # Linter - analisa sintaxe, não importa seus módulos uvx black . # Formatter - manipula texto, não importa seus módulos uvx mypy . # Type checker - analisa tipos, não precisa rodar seu código uvx isort . # Organizador de imports - só lê arquivos uvx ruff@latest check . # Use specific version
uv run uses your project's existing virtual environment. Use it for tools that: Need to import your project modules Are part of your development workflow with project dependencies Run tests or your application uv run pytest tests/ # Test runner - precisa importar seus módulos uv run python main.py # Sua aplicação uv run python -m myapp.cli # CLI do seu app uv run dbt run # dbt com suas transformações do projeto
If the project already uses uv run for a specific tool, continue using it. If you see uv run ruff check . in the project, don't change to uvx If the user specified uv run pytest, maintain the pattern Project consistency takes precedence over the "ideal rule" Why? Changing from uv run to uvx (or vice-versa) mid-project can: Break scripts/CI that expect the specific command Confuse other developers Create unnecessary inconsistency
NEVER run thisALWAYS run this insteadpython script.pyuv run python script.pypython -c "import..."uv run python -c "import..."python -m moduleuv run python -m modulepython3 script.pyuv run python3 script.pydbt --versionuv run dbt --versiondbt runuv run dbt rundbt debuguv run dbt debugdbt depsuv run dbt depspytestuv run pytest (imports project modules) or uvx pytest (one-off)pytest tests/uv run pytest tests/ (imports project modules) or uvx pytest tests/ (one-off)black .uvx black . (preferred - external tool) or uv run black . (if already in project)ruff check .uvx ruff check . (preferred - external tool) or uv run ruff check . (if already in project)mypy .uvx mypy . (preferred - external tool) or uv run mypy . (if already in project)pip install <package>uv add <package>pip install -r requirements.txtuv pip install -r requirements.txtpip listuv pip listpip freezeuv pip freeze
Use when: Installing ANY Python package or dependency (for ANY Python app: web apps, scripts, data processing, dbt, ML, etc.) Setting up Python projects (web apps like Flask/Django/FastAPI, data science, ML, automation, dbt, etc.) Installing dependencies for ANY Python-based application Creating virtual environments Running Python scripts Running tests (pytest, unittest, etc.) Using dbt commands (dbt-core, dbt-snowflake, etc.) ANY task involving Python packages or dependencies
NEVER use these pip commands. ALWAYS use the uv equivalent: NEVER use pipALWAYS use uvpip install <package>uv add <package>pip install -r requirements.txtuv pip install -r requirements.txtpip listuv pip listpip freezeuv pip freeze
These are commonly installed Python packages that have CLI commands. When installing or running them, always use uv: ToolInstall with uvRun with uv (project)Run with uvx (external)dbt (dbt-core)uv add dbt-snowflake (or dbt-postgres)uv run dbt <command>-pytestuv add pytestuv run pytest (imports project modules)uvx pytest (one-off)black (formatter)uv add blackuv run black (if in project)uvx black . (preferred)ruff (linter)uv add ruffuv run ruff (if in project)uvx ruff check . (preferred)mypy (type checker)uv add mypyuv run mypy (if in project)uvx mypy . (preferred)flake8 (linter)uv add flake8uv run flake8uvx flake8pylint (linter)uv add pylintuv run pylintuvx pylintisort (import sorter)uv add isortuv run isortuvx isort .poetry (dependency manager)uv add poetryuv run poetryuvx poetrypipenv (dependency manager)uv add pipenvuv run pipenvuvx pipenvcookiecutter (project templates)uv add cookiecutteruv run cookiecutteruvx cookiecutterhttpie (HTTP client)uv add httpieuv run httpuvx httpmycli (MySQL CLI)uv add mycliuv run mycliuvx myclipgcli (PostgreSQL CLI)uv add pgcliuv run pgcliuvx pgcli Note: For linters, formatters, and type checkers, uvx is preferred (doesn't pollute project dependencies). For tools that need to import your project modules (like pytest with your app code), use uv run.
For ANY Python package with a CLI command: # Option 1: Run as external tool (preferred for linters, formatters, one-off tools) uvx <cli-command> # Option 2: Install and run within project environment uv add <package> uv run <cli-command> # Option 3: Run with specific version uvx <package>@version <cli-command>
NEVER use pipALWAYS use uvpython -m venv .venvuv venvpython script.pyuv run script.pypython -m moduleuv run python -m modulepython -m pip installuv addpython -m pip listuv pip list
uv (with uv run or uvx) is the ONLY option for Python package management and execution. Execution priority: uv run <command> - for tools that need project dependencies uvx <command> - for external tools that don't need project modules Only consider pip as a fallback if: The user explicitly requests pip uv is not available on the system You receive explicit confirmation from the user
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.