windows-expert
Provides practical guidance for Windows-WSL interoperability tasks including path conversion, executable calling, and system administration. Covers common pain points like file permissions, line endings, and networking quirks. Focuses on actionable commands rather than theoretical concepts.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install jackspace-claudeskillz-windows-expert
Repository
Skill path: skills/windows-expert
Provides practical guidance for Windows-WSL interoperability tasks including path conversion, executable calling, and system administration. Covers common pain points like file permissions, line endings, and networking quirks. Focuses on actionable commands rather than theoretical concepts.
Open repositoryBest for
Primary workflow: Run DevOps.
Technical facets: DevOps.
Target audience: Developers and system administrators working with Windows-WSL environments, particularly those doing cross-platform development or managing mixed environments.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: jackspace.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install windows-expert into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/jackspace/ClaudeSkillz before adding windows-expert to shared team environments
- Use windows-expert for devops workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
--- 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