agentleFS
BenknightdarkBenknightdark/neo-skills/skills/neo-python-manager/SKILL.md

neo-python-manager

Skill7 starsChanged 6 months agoMITView on GitHub

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.

  • Pipes a download into a shell
  • Installs packages

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check the system environment to test if tools are installed: execute uv --version or poetry --version.

    line 25
  2. Very specific:

    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 …

    line 28
  3. Distinctive:

    Tool Installation Suggestion: If the tool is not installed, must ask the user first: "Detected that the project uses [Tool Name], but it is …

    line 30
  4. Distinctive:

    Execute Changes: If the user agrees to installation or dependency changes, provide CLI commands for user confirmation.

    line 32
  5. Very specific:

    Detection Criteria: Only requirements.txt or .venv exists.

    line 54
  6. Distinctive:

    Installation and Operation Guidance: If tools are missing, proactively ask for installation consent and provide the correct syntax.

    line 61
  7. Distinctive:

    Environment Consistency Check: Ensure provided commands perfectly match the project's existing lock files.

    line 62
  8. Distinctive:

    Never execute installation commands directly without asking the user.

    line 65

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. 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.
  2. 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".
  3. 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).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.