Windows Expert
- 142 installs
- 16 repo stars
- Updated November 20, 2025
- jackspace/claudeskillz
Solve Windows-specific dev tasks: PowerShell, WSL boundaries, paths, services, installers, and desktop automation quirks on Win32.
About
Windows-expert equips Claude to give correct Windows development and automation advice: shells, environment setup, file locking, services, and packaging differences from Unix. Use when scripts fail on Windows CI, users run agents locally on Win32, or docs must cover PowerShell equivalents.
- PowerShell and cmd best practices
- Path, permissions, and service troubleshooting
- WSL vs native Windows guidance
- Installer and registry-aware workflows
- Desktop automation edge cases
Windows Expert by the numbers
- 142 all-time installs (skills.sh)
- +2 installs in the week ending Aug 2, 2026 (Skillselion tracking)
- Ranked #226 of 550 CLI & Terminal skills by installs in the Skillselion catalog
- Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/jackspace/claudeskillz --skill windows-expertAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 142 |
|---|---|
| repo stars | ★ 16 |
| Last updated | November 20, 2025 |
| Repository | jackspace/claudeskillz ↗ |
What it does
Solve Windows-specific dev tasks: PowerShell, WSL boundaries, paths, services, installers, and desktop automation quirks on Win32.
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)
Examples
Add examples of how to use this skill here.
Notes
- This skill was auto-generated
- Edit this file to customize behavior
{
"sections": {
"Notes": "- This skill was auto-generated\n- Edit this file to customize behavior",
"Instructions": "When helping with Windows-related tasks:\n- Use /mnt/c/ paths for Windows drives in WSL\n- Use wslpath for path conversion: wslpath -w (Linux to Windows), wslpath -u (Windows to Linux)\n- Windows executables can be called from WSL: cmd.exe, powershell.exe, *.exe\n- Be aware of file permissions and line ending differences (CRLF vs LF)\n- Provide PowerShell examples alongside bash when relevant\n- Use modern PowerShell conventions (cmdlets, pipelines)\n- Suggest PowerShell Core (pwsh) for cross-platform scripts\n- Help with Registry operations (Get-ItemProperty, Set-ItemProperty)\n- Windows Services management\n- Task Scheduler for automation\n- Windows networking (netsh, Get-NetAdapter)\n- NTFS permissions and ACLs\n- Path length limitations (260 char limit)\n- Case sensitivity differences\n- Drive letter handling\n- Windows Defender/Firewall interactions\n- WSL2 networking quirks (bridge mode, port forwarding)",
"Examples": "Add examples of how to use this skill here."
},
"id": "windows-expert",
"name": "windows-expert",
"description": "Expert guidance for Windows, PowerShell, WSL interop, and cross-platform development"
}---
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
Related skills
Lark SharedWire Feishu/Lark Open Platform auth, tokens, and shared API helpers into agent-built bots and internal tools.493k
Runcomfy CliLet their coding agent call any RunComfy model from the terminal or scripts without managing separate SDKs.298k30
Skills CliDiscover, install, update, and manage reusable agent capabilities from the open Skillselion ecosystem directly inside their coding agent.270k72TzstCreate, extract, list, and script `.tzst` / `.tar.zst` archives from the terminal with the right compression, streaming, and conflict flags.267k72XdropPull files from an Xdrop share URL, decrypt them locally, and land outputs in a chosen directory with optional JSON for automation.266k72
WizardAuthor interactive bash setup wizards that open URLs, capture secrets, write .env upserts, and set GitHub Actions secrets step by step.92.1k193k