Environment Triage
- 458 installs
- 3.9k repo stars
- Updated January 26, 2026
- parcadei/continuous-claude-v3
environment-triage is an agent skill that diagnoses Python environment mismatches when uv sync or pip install fails by checking the active uv interpreter, .python-version pin, and package import versions.
About
environment-triage is a Claude Code skill from parcadei/continuous-claude-v3 for debugging Python dependency issues caused by interpreter mismatches rather than missing packages. The skill runs uv run python --version, inspects .python-version pins that control uv's interpreter, verifies installs with uv pip show, and confirms imports via uv run python -c. A common fix bumps .python-version to 3.12+ when optional deps require newer Python than a 3.11 pin. Developers reach for environment-triage when uv sync behaves unexpectedly, imports fail despite pip reporting success, or system Python disagrees with the uv-selected virtual environment.
- environment-triage
Environment Triage by the numbers
- 458 all-time installs (skills.sh)
- +2 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #936 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/parcadei/continuous-claude-v3 --skill environment-triageAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 458 |
|---|---|
| repo stars | ★ 3.9k |
| Last updated | January 26, 2026 |
| Repository | parcadei/continuous-claude-v3 ↗ |
Why does uv sync use the wrong Python version?
Use environment-triage for development tasks
Who is it for?
Python developers using uv who hit mysterious install or import failures across system Python and project virtualenvs.
Skip if: Node or JVM projects without uv-managed Python environments should skip environment-triage.
When should I use this skill?
uv sync or pip install fails unexpectedly, imports break after install, or system Python differs from the uv-selected interpreter.
What you get
Verified uv interpreter, corrected .python-version pin, confirmed package install, and working import in uv context
- Verified interpreter selection
- Corrected .python-version pin
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-extrasDON'T
- Trust
python3 --versionwhen 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.12marker, but uv was using 3.11 - 4784f390: agentica import failures traced to wrong interpreter
Related skills
Lark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.493k
Lark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.387k16kLark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.386k16k
Just ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k41Lark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.235k16k
Design An InterfaceGenerate multiple radically different interface or API designs in parallel before committing to one.188k198kHow it compares
Use environment-triage before rewriting dependency files when the symptom is interpreter mismatch under uv.
FAQ
What commands does environment-triage recommend first?
environment-triage starts with uv run python --version, cat .python-version, uv pip show for the package, and uv run python -c import checks. These confirm which interpreter and packages uv actually uses.
When should developers bump .python-version?
environment-triage suggests raising .python-version to 3.12 or newer when optional dependencies require Python 3.12+ but the project pin still targets 3.11, then recreating the virtual environment.