Neo python manager

Skill Benknightdark/neo-skills/skills/neo-python-manager

Neo Skills 是專為現代 AI Agent 設計的全方位能力擴充套件。本專案透過標準化的通訊架構，為 AI 代理安裝可插拔的「技能模組 (Skills)」，使其不僅僅是一個聊天機器人，而是能轉化為具備「感知-推理-行動」能力的多領域專家。

Install

npx -y skills add Benknightdark/neo-skills --skill neo-python-manager

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use this skill when the user asks how to install, add, remove, update, or run Python dependencies; choose between uv, Poetry, venv, or pip; create/sync a virtual environment; or diagnose Python package manager setup from pyproject.toml, lock files, or requirements.txt.

SKILL.md

3.5 KB, as published. Nobody here has run it

Python Environment Manager Skill

Trigger On

The user asks "How do I install a package?" or "Which package manager is this project using?".
The user requests to add, remove, or update Python dependencies.
Need to initialize a virtual environment or execute a Python script but unsure whether to use uv run, poetry run, or python.
The project lacks explicit environment configuration and needs recommendations for suitable tools.

Workflow

Perceive:
- Scan the project root for characteristic files: uv.lock, poetry.lock, pyproject.toml, requirements.txt.
- Check the system environment to test if tools are installed: execute uv --version or poetry --version.
Reason:
- Determine the tool the project should use based on characteristic files (Priority: uv > Poetry > pip).
- Check tool availability: If the project is determined to use uv but it's not installed, or if the user wants to switch to uv/Poetry but the environment is not ready, mark it as "Pending Installation".
Act:
- Tool Installation Suggestion: If the tool is not installed, must ask the user first: "Detected that the project uses [Tool Name], but it is not installed in your environment. Would you like me to provide the installation command and assist with the installation?"
- Output Commands: Provide the correct operation commands for the identified management tool.
- Execute Changes: If the user agrees to installation or dependency changes, provide CLI commands for user confirmation.

Tooling Commands Reference

1. uv (Recommended: Ultra-fast Tool)

Detection Criteria: uv.lock exists.
Installation (Unix/macOS): curl -LsSf https://astral.sh/uv/install.sh | sh
Installation (Windows): powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
Common Commands:
- uv add <package> (Add package)
- uv sync (Sync environment)
- uv run <script.py> (Run script)

2. Poetry

Detection Criteria: poetry.lock exists or [tool.poetry] in pyproject.toml.
Installation (Cross-platform): curl -sSL https://install.python-poetry.org | python3 -
Common Commands:
- poetry add <package> (Add package)
- poetry install (Install dependencies)
- poetry run python <script.py> (Run script)

3. venv + pip (Legacy Standard)

Detection Criteria: Only requirements.txt or .venv exists.
Common Commands:
- pip install <package>
- pip install -r requirements.txt

Deliver

Environment Detection Report: Inform the current environment status (e.g., uv installed, poetry.lock detected).
Installation and Operation Guidance: If tools are missing, proactively ask for installation consent and provide the correct syntax.
Environment Consistency Check: Ensure provided commands perfectly match the project's existing lock files.

Validate

Never execute installation commands directly without asking the user.
Installation commands must distinguish between operating systems (macOS/Linux vs Windows).