python-env-unblocker

Create or locate a local .venv and configure VS Code Python interpreter settings.

2|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/anyekoutouming/anyekoutouming --skill python-env-unblocker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: python-env-unblocker
Source: https://github.com/anyekoutouming/anyekoutouming/tree/main/python-env-unblocker
Command: npx skills add https://github.com/anyekoutouming/anyekoutouming --skill python-env-unblocker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

In new Python workspaces, the interpreter can be unselected, the terminal may not activate the environment, or imports fail because a local .venv is missing or misconfigured. This Skill automates locating or creating a local .venv and wiring the project to use it in VS Code.

Core Features & Use Cases

  • Detects missing or misconfigured Python environments in a workspace and suggests a fix.
  • Creates or reuses a local .venv and updates [workspace]/.vscode/settings.json to point the interpreter to the virtual environment and enable terminal activation.
  • Verifies the environment by running a quick check to ensure the interpreter path resolves correctly.

Quick Start

Run the repair workflow in your project workspace to locate or create a .venv and update the workspace settings.

Frequently Asked Questions about python-env-unblocker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix Python interpreter not selected in VS Code workspace?

To fix the Python interpreter not selected in VS Code workspace, you need to locate or create a local .venv and update .vscode/settings.json with python.defaultInterpreterPath. This automatically wires the interpreter and resolves the missing environment.

Why does my Python terminal fail to activate the virtual environment automatically?

Your Python terminal fails to activate the virtual environment automatically because python.terminal.activateEnvironment is missing or disabled in .vscode/settings.json. Updating this workspace setting ensures terminal activation matches the local .venv.

How to resolve failing imports caused by a missing .venv in a Python project?

To resolve failing imports caused by a missing .venv in a Python project, generate a local virtual environment and configure python.analysis.extraPaths in the .vscode/settings.json file. This wires the interpreter correctly and fixes the import resolution.

Does this workspace setup approach require existing dependencies or plugins?

This workspace setup approach requires no external dependencies or plugins to function. It uses scripts to detect or generate a local .venv and directly modifies the .vscode/settings.json file to wire the interpreter path.

What is the best way to configure VS Code settings for a new Python workspace?

The best way to configure VS Code settings for a new Python workspace is to automate the generation of .vscode/settings.json with python.defaultInterpreterPath and python.terminal.activateEnvironment. This verifies interpreter availability and ensures consistent environment activation.