python-venv

Create a project-root Python virtual environment and install dependencies from requirements.txt.

3|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/eamars/KazusaAIChatbot --skill python-venv-eamars
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: python-venv
Source: https://github.com/eamars/KazusaAIChatbot/tree/main/.agents/skills/python-venv
Command: npx skills add https://github.com/eamars/KazusaAIChatbot --skill python-venv-eamars

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes a consistent, isolated Python virtual environment at the project root to prevent pollution of the global Python installation and drift across projects.

Core Features & Use Cases

  • Checks for an existing venv at the project root and reuses it when available.
  • Creates the venv at <project_root>/venv/ only if missing, ensuring a standard location.
  • Installs dependencies from a provided requirements.txt and verifies that key packages import correctly.

Quick Start

If no venv exists at the project root, create venv at venv/, then install dependencies from a provided requirements.txt and verify key packages.

Frequently Asked Questions about python-venv

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I isolate Python dependencies to prevent global site-packages pollution?

Python dependency isolation is achieved by creating a virtual environment at the project root, which prevents global site-packages pollution and ensures consistent dependency versions.

What is the best way to set up a Python virtual environment using requirements.txt?

Setting up a Python virtual environment involves checking for an existing venv at the project root, creating one if missing, and installing dependencies from a requirements.txt file to verify key packages.

Does Python venv setup reuse an existing virtual environment at the project root?

Yes, virtual environment setup checks for an existing venv at the project root and reuses it when available. It only creates a new venv if one is currently missing.

Why do I need a project-root virtual environment for Python development?

A project-root virtual environment is needed to prevent drift across projects and isolate dependencies. It establishes a standard venv location to verify package imports safely.

Can I verify package imports after installing dependencies in a Python venv?

Yes, you can verify package imports after installing dependencies in a Python venv. The setup process explicitly checks that key packages import correctly following installation.

What happens if an existing venv is missing during Python environment setup?

If an existing venv is missing during Python environment setup, a new virtual environment is created at venv/ in the project root, followed by dependency installation and import verification.