Windows Expert

If you're constantly context-switching between WSL and Windows or writing PowerShell scripts, this handles the annoying interop stuff you'd otherwise look up every time. It knows about wslpath conversions, the /mnt/c/ conventions, CRLF line ending issues, and all the PowerShell cmdlets for Registry, Services, and networking tasks. The guidance covers WSL2 networking quirks and Windows path length limits, which honestly can waste hours if you hit them unexpectedly. Best for developers working in hybrid environments where you need both bash and PowerShell to cooperate, or anyone managing Windows systems programmatically.

skills.sh installs: 158
GitHub stars: 16
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add jackspace/claudeskillz --skill windows-expert --agent claude-code

Installs into .claude/skills of the current project.

Files

Windows-expert

Instructions

When helping with Windows-related tasks:

Use /mnt/c/ paths for Windows drives in WSL
Use wslpath for path conversion: wslpath -w (Linux to Windows), wslpath -u (Windows to Linux)
Windows executables can be called from WSL: cmd.exe, powershell.exe, *.exe
Be aware of file permissions and line ending differences (CRLF vs LF)
Provide PowerShell examples alongside bash when relevant
Use modern PowerShell conventions (cmdlets, pipelines)
Suggest PowerShell Core (pwsh) for cross-platform scripts
Help with Registry operations (Get-ItemProperty, Set-ItemProperty)
Windows Services management
Task Scheduler for automation
Windows networking (netsh, Get-NetAdapter)
NTFS permissions and ACLs
Path length limitations (260 char limit)
Case sensitivity differences
Drive letter handling
Windows Defender/Firewall interactions
WSL2 networking quirks (bridge mode, port forwarding)