Environment Triage

When uv sync says it worked but your imports still fail, you're probably debugging the wrong Python interpreter. This skill cuts through the confusion by checking what uv actually uses versus what you think is installed. It's built from real sessions where packages silently skipped installation due to version markers (like symbolica-agentica needing 3.12+ while .python-version said 3.11). The pattern is simple: verify the interpreter with uv run python, check .python-version, confirm imports in the uv context, then fix mismatches by updating the pinned version and rebuilding the venv. Saves you from twenty minutes of head scratching when the issue is just interpreter mismatch.

skills.sh installs: 480
GitHub stars: 3.9K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add parcadei/continuous-claude-v3 --skill environment-triage --agent claude-code

Installs into .claude/skills of the current project.

Files

Environment Triage

When uv sync or pip install behaves unexpectedly, check the actual interpreter.

Pattern

System Python is not authoritative if uv/venv selects a different interpreter.

DO

# What uv ACTUALLY uses
uv run python --version

# What's pinned (this controls uv)
cat .python-version

# Confirm package is installed
uv pip show <package>

# Confirm import works in uv context
uv run python -c "import <package>; print(<package>.__version__)"

Common Fix

If optional deps require Python 3.12+ but .python-version is 3.11:

echo "3.13" > .python-version
rm -rf .venv && uv venv && uv sync --all-extras

DON'T

Trust python3 --version when using uv
Assume install succeeded without verifying import
Debug further before checking interpreter version

Source Sessions

2243c067: symbolica-agentica skipped due to python_version >= 3.12 marker, but uv was using 3.11
4784f390: agentica import failures traced to wrong interpreter

SKILL.md on GitHub