What problem does it solve? Setting up isolated Python environments manually is error-prone: packages leak into the system Python, wrong interpreter versions get used, and virtual environment directories end up committed to git. This Skill creates, validates, or re-creates a project-local virtual environment with strict guardrails that never touch the host system Python. ## Core Features & Use Cases - Managed environment lifecycle: Create, re-create, validate, or delete a single managed environment (default .venv) at a user-specified name or path, with version matching against the requested Python release. - Safe package installation: Install packages or requirements files using only the managed environment's own pip, never the host pip or another environment. - Repository hygiene: Automatically add the environment directory to .gitignore and to galaxy.yml build_ignore when present. - Use Case: Before running a project's test suite or CLI tooling locally, ask the agent to set up .venv with Python 3.11 and install requirements.txt, then reuse <managed-env>/bin/python for all subsequent commands. ## Quick Start Set up a Python virtual environment at .venv using Python 3.11 and install the packages from requirements.txt into it.
