python-import-path-debugging
Diagnose ModuleNotFoundError when a package is installed but still fails to import
Best use case
python-import-path-debugging is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Diagnose ModuleNotFoundError when a package is installed but still fails to import
Teams using python-import-path-debugging should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/python-import-path-debugging/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How python-import-path-debugging Compares
| Feature / Agent | python-import-path-debugging | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Diagnose ModuleNotFoundError when a package is installed but still fails to import
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Python Import Path Debugging When a ModuleNotFoundError occurs despite the package being installed, the issue is typically a Python path/environment mismatch. Check: (1) which Python executable the CLI script uses (check shebang and `which`), (2) which environment has the package installed vs. which the script is executing in, (3) whether the script is using a virtual environment that differs from your active shell environment. Verify with `python -c "import module; print(module.__file__)"` to confirm the correct interpreter is being used.
Related Skills
test-driven-hook-debugging
Debugging and fixing shell hooks by writing isolated test suites first, then using test failures to pinpoint logic bugs
tax-software-duplicate-adjustment-debugging
Identify and fix duplicate tax adjustments entered through multiple mechanisms in tax software
python-import-path-mismatch-debugging
Diagnose and fix ModuleNotFoundError when a package is installed but imports still fail due to environment/path mismatches
multi-layer-stale-state-debugging
Detect and clear stale state persisting across multiple storage layers (auth files, cache, code logic)
diagnose-venv-shebang-import-errors
Debugging pattern for ModuleNotFoundError when CLI entry points use wrong Python interpreter
diagnose-shebang-virtualenv-import-errors
Debugging pattern for ModuleNotFoundError when CLI entry points use wrong Python interpreter
diagnose-shebang-venv-import-errors
Troubleshoot ModuleNotFoundError in CLI tools by identifying shebang-venv mismatches
batch-regex-fix-import-syntax
Detect and fix mid-import blank-line syntax breaks across multiple files using line-based regex
awk-range-pattern-edge-case-debugging
Debugging technique for awk range patterns that collapse when start line matches end pattern
learned-git-worktree-hook-path-and-real-hook-shape-review
Catch hook-installation and governance bugs that only appear in linked git worktrees or against the real generated hook shape, not simplified test fixtures.
provider-audit-bootstrap-and-path-classification
Fix provider-session ecosystem audit failures caused by source-checkout imports and over-aggressive symbolic-path classification.
overnight-worktree-uv-warmup-and-log-path-guardrails
Prevent false stalls and missing-log failures in overnight Codex worktree batches by pre-warming uv environments, using exact log-path directory creation, and interpreting buffered logs correctly.