wsl-bash-windows

Diagnose and guide shell, path, and network execution in Windows and WSL mixed environments.

7|1|Updated May 9, 2026
One-click install
npx skills add https://github.com/black-yt/skills --skill wsl-bash-windows
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wsl-bash-windows
Source: https://github.com/black-yt/skills/tree/main/wsl-bash-windows
Command: npx skills add https://github.com/black-yt/skills --skill wsl-bash-windows

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you work correctly in Windows + WSL projects when shell execution, path handling, networking, or Git operations fail because the environment is mixed between Windows and Linux.

Core Features & Use Cases

  • WSL Environment Detection: Confirms when a project is actually running under WSL and when an execution failure is caused by a bad sandbox or broken shell binding.
  • Windows-to-WSL Path Handling: Converts and validates Windows paths, mounted drive paths, and user-shared image locations so commands and file reads work in the right filesystem.
  • Safe Push and Network Troubleshooting: Guides GitHub and Hugging Face pushes, token environment checks, DNS diagnosis, proxy inspection, and permission escalation when network or credential issues appear.
  • Operational Guardrails: Prevents accidental switching to PowerShell, CMD, or Windows Node when the task must stay in WSL Bash, and emphasizes safe file editing and verification.

Quick Start

Use the wsl-bash-windows skill to verify my current shell, diagnose any WSL or sandbox startup failure, and give me the safest next command for this Windows + WSL workspace.

Frequently Asked Questions about wsl-bash-windows

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

FAQPage Schema
How do I fix Git push failures from WSL Bash on Windows?

Git push failures in WSL Bash often stem from credential or mixed shell path issues. This Skill diagnoses shell binding, validates token environment variables, and guides safe push handling without forcing a switch to PowerShell or Windows tooling.

Why does my WSL Bash fail to read Windows file paths?

WSL Bash fails to read Windows paths because it expects Linux-style mounted drive paths. This Skill converts and validates Windows-origin image locations and mounted drive paths so commands execute in the correct filesystem.

How do I troubleshoot DNS and proxy issues inside WSL?

DNS and proxy issues inside WSL require inspecting network configuration specific to the Linux subsystem. This Skill guides DNS diagnosis, proxy inspection, and permission escalation to resolve network connectivity failures within WSL Bash.

Can I use Hugging Face push commands from WSL without Windows Node?

Yes, you can execute Hugging Face push commands from WSL without Windows Node. This Skill ensures token-aware push handling and enforces operational guardrails to prevent accidental switching to Windows tooling during execution.

What is the best way to diagnose WSL sandbox startup failures on Windows?

Diagnosing WSL sandbox startup failures requires confirming whether the project is actually running under WSL. This Skill detects the WSL environment, identifies broken shell bindings, and provides the safest next command for the mixed workspace.

Does WSL Bash support switching to PowerShell when commands fail?

Switching to PowerShell when WSL Bash commands fail is strongly discouraged. This Skill applies operational guardrails to keep execution in WSL Bash, emphasizing safe file editing and verification steps rather than switching to Windows tooling.