KiloClawPowered by OpenClaw
Back to Cookbook
OpenClaw recipe

Env Doctor

Fix Python dependency hell without losing your afternoon

Diagnose and fix conda/pip conflicts, generate reproducible environment files, and containerize analytics projects. No more "it works on my machine" or spending an entire day getting dependencies to resolve.

CommunitySubmitted by CommunityWork1 min
Try in KiloClawFree 7-day trial

PROMPT

Create a skill called "Env Doctor". Help me diagnose and fix Python environment issues. When I paste an error message (dependency conflicts, ImportError, version mismatches, conda solver failures), identify the root cause and provide a specific fix. When I point you at a Python project, analyze all imports and generate the minimal environment file (requirements.txt, environment.yml, or pyproject.toml) needed to run it. Detect conda/pip mixing issues (packages installed by both managers). If an environment is beyond repair, generate a Dockerfile that creates a clean, reproducible environment. Support conda, pip, poetry, and uv. For data science projects, know the common conflict patterns (e.g., numpy binary compatibility, tensorflow + CUDA version matrix, scikit-learn + scipy version coupling).

How It Works

Analytics teams lose entire days to Python environment issues — conda solver

hanging for hours, pip and conda fighting over numpy versions, a colleague's

notebook that only runs on their machine. This skill untangles the mess.

What You Get

  • Dependency conflict diagnosis from error messages
  • Auto-generated environment files (requirements.txt, environment.yml, pyproject.toml)
  • Conda/pip conflict detection and resolution
  • Environment recreation from a script's import statements
  • Docker containerization for reproducible execution
  • Migration between conda, pip, poetry, and uv

Setup Steps

  1. Ask your Claw to create an "Env Doctor" skill with the prompt below
  2. Paste the error message, point it at your project, or describe the issue
  3. Get back a diagnosis and fix

Tips

  • Prevention beats cure: run the audit before sharing code with teammates
  • The Docker containerization is the nuclear option when nothing else works
  • uv is often the fastest fix for pip dependency resolution issues
  • For data science stacks (numpy, scipy, scikit-learn, pandas), the skill knows the common version conflicts
Tags:#python#environment#devops#productivity

Related Recipes

Morning Kickstart

One command to start everything, every morning

Docker, Postgres, Redis, frontend, backend, worker — if you start the same stack every morning, this recipe turns that repeated setup into one command and a clearer startup flow.

Work3 min setup

Dialect Flip

Translate SQL between any two databases instantly

Paste SQL written for one database and get the equivalent for another. Handles the syntax nightmares — DATEADD vs DATE_ADD, QUALIFY, LIMIT vs TOP, string functions, NULL handling — across Postgres, MySQL, BigQuery, Snowflake, Redshift, SQL Server, and more.

Work1 min

Tech Radar

Keep up with what matters, ignore the hype

Set up a lightweight weekly digest around your stack and interests. A nice starter automation because it shows OpenClaw doing recurring research without requiring a huge workflow or lots of context.

Personal3 min setup

Bookmark Rescuer

Your Pocket/bookmarks graveyard, resurrected

Export your bookmarks and your Claw turns the pile into something usable: categorizes links, summarizes unread items, spots dead links, and helps you find what you saved later.

Personal5 min