Expert guidance for Windows, PowerShell, WSL interop, and cross-platform development
Pro scans all 3 files and shows the line behind each finding
Scanned 2/12/2026
npx -y skills add jackspace/ClaudeSkillz --skill windows-expert --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Windows Expert?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/jackspace-windows-expert)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: windows-expert
description: Expert guidance for Windows, PowerShell, WSL interop, and cross-platform development
---
# 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)
## Examples
Add examples of how to use this skill here.
## Notes
- This skill was auto-generated
- Edit this file to customize behavior
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!