How do I install the Windows Development skill?

Run npx skillmds@latest add tomevault-io/windows-development in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Windows Development safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Windows Development?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Windows Development free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Windows Development?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Windows Development by tomevault-io

Name: Windows Development
Author: tomevault-io

Windows Development

Windows-specific development patterns, registry operations, shell integration, and path handling. Use when working with Windows registry, Explorer context menus, shell extensions, batch files, Windows Terminal configuration, or any task requiring Windows-specific knowledge about quoting, escaping, and path handling. Use when this capability is needed.

tomevault-io c6e1c16 2 files · 4.9 KB Updated Sep 17, 2026

File contents

ALWAYS use PowerShell's native registry provider:

# Create key
$path = "Registry::HKEY_CLASSES_ROOT\Directory\shell\MyEntry"
$null = New-Item -Path $path -Force
Set-ItemProperty -Path $path -Name "(Default)" -Value "My Menu Item"
Set-ItemProperty -Path $path -Name "Icon" -Value "myapp.exe"

# Create command subkey
$null = New-Item -Path "$path\command" -Force
Set-ItemProperty -Path "$path\command" -Name "(Default)" -Value 'myapp.exe "%1"'

Before writing new registry entries, ALWAYS examine existing working examples:

# List all context menu entries
reg query "HKEY_CLASSES_ROOT\Directory\shell"

# Show specific entry with command
reg query "HKEY_CLASSES_ROOT\Directory\shell\<entry>\command"

# Full recursive dump
reg query "HKEY_CLASSES_ROOT\Directory\shell" /s

# GOOD - quotes preserved
$cmd = 'wsl.exe --cd "%1"'

# BAD - quotes may be stripped
$cmd = "wsl.exe --cd `"%1`""

Always use -LiteralPath instead of -Path for paths with special characters:

Set-Location -LiteralPath $folderPath  # Handles [brackets], spaces, etc.

Create test folder: D:\Test Folder With Spaces
Create test folder: D:\Test[Brackets]
Test BOTH right-click scenarios:
- Right-click ON the folder
- Right-click INSIDE the folder (empty space)

Verify registry entries after creation:

reg query "HKEY_CLASSES_ROOT\Directory\shell\YourEntry\command"

Common WT commands:

wt.exe -d "path"                    # Open at directory (uses default profile)
wt.exe -p "Profile Name" -d "path"  # Specific profile
wt.exe -p "Command Prompt" -d "path" cmd /k command  # CMD with command

# PowerShell script with proper parameter handling
param([string]$Path)
& wt.exe -d $Path

If batch files are required, use %~1 to strip outer quotes:

@echo off
wt.exe -d "%~1"

cmd.exe /s /k pushd "%V"
powershell.exe -NoExit -Command Set-Location -LiteralPath '%V'
wsl.exe --cd "%V"
wt.exe -d "%V" -p "Command Prompt"
"C:\Program Files\App\app.exe" "%1"

Check if \command subkey exists: reg query "...\command"
Verify quotes are preserved in the command value
Test with a simple path first (no spaces)
Test with a path containing spaces
Check Windows Event Viewer for errors
Try running the command manually in cmd/PowerShell

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: windows-developmentdescription: Windows-specific development patterns, registry operations, shell integration, and path handling. Use when working with Windows registry, Explorer context menus, shell extensions, batch files, Windows Terminal configuration, or any task requiring Windows-specific knowledge about quoting, escaping, and path handling. Use when this capability is needed.---<critical_lessons><lesson name="registry_operations">**NEVER use `reg.exe` for commands containing quotes** - quotes get stripped unpredictably.**ALWAYS use PowerShell's native registry provider:**```powershell# Create key$path = "Registry::HKEY_CLASSES_ROOT\Directory\shell\MyEntry"$null = New-Item -Path $path -ForceSet-ItemProperty -Path $path -Name "(Default)" -Value "My Menu Item"Set-ItemProperty -Path $path -Name "Icon" -Value "myapp.exe"# Create command subkey$null = New-Item -Path "$path\command" -ForceSet-ItemProperty -Path "$path\command" -Name "(Default)" -Value 'myapp.exe "%1"'```**Before writing new registry entries, ALWAYS examine existing working examples:**```powershell# List all context menu entriesreg query "HKEY_CLASSES_ROOT\Directory\shell"# Show specific entry with commandreg query "HKEY_CLASSES_ROOT\Directory\shell\<entry>\command"# Full recursive dumpreg query "HKEY_CLASSES_ROOT\Directory\shell" /s```</lesson><lesson name="context_menu_locations">| Location | Trigger ||----------|---------|| `Directory\shell` | Right-click ON a folder || `Directory\Background\shell` | Right-click INSIDE a folder (empty space) |</lesson><lesson name="path_variables">| Variable | Meaning | Use Case ||----------|---------|----------|| `%1` | Selected item path | Right-click on folder || `%V` | Current directory | Right-click inside folder |</lesson><lesson name="quoting_and_escaping">**Single quotes survive better than escaped double quotes in PowerShell strings:**```powershell# GOOD - quotes preserved$cmd = 'wsl.exe --cd "%1"'# BAD - quotes may be stripped$cmd = "wsl.exe --cd `"%1`""```**Always use `-LiteralPath` instead of `-Path` for paths with special characters:**```powershellSet-Location -LiteralPath $folderPath # Handles [brackets], spaces, etc.```</lesson><lesson name="testing_approach">**ALWAYS test with edge cases immediately:**1. Create test folder: `D:\Test Folder With Spaces`2. Create test folder: `D:\Test[Brackets]`3. Test BOTH right-click scenarios: - Right-click ON the folder - Right-click INSIDE the folder (empty space)4. Verify registry entries after creation: ```powershell reg query "HKEY_CLASSES_ROOT\Directory\shell\YourEntry\command" ```</lesson><lesson name="windows_terminal">**Profile names must match exactly** - check settings.json:```%LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json```**Common WT commands:**```powershellwt.exe -d "path" # Open at directory (uses default profile)wt.exe -p "Profile Name" -d "path" # Specific profilewt.exe -p "Command Prompt" -d "path" cmd /k command # CMD with command```</lesson><lesson name="batch_vs_powershell">**Avoid batch files for complex quoting** - use PowerShell scripts instead:```powershell# PowerShell script with proper parameter handlingparam([string]$Path)& wt.exe -d $Path```**If batch files are required, use `%~1` to strip outer quotes:**```batch@echo offwt.exe -d "%~1"```</lesson></critical_lessons><proven_patterns>These patterns are proven to work from registry entries:```textcmd.exe /s /k pushd "%V"powershell.exe -NoExit -Command Set-Location -LiteralPath '%V'wsl.exe --cd "%V"wt.exe -d "%V" -p "Command Prompt""C:\Program Files\App\app.exe" "%1"```</proven_patterns><debugging_checklist>When context menu entries don't work:1. [ ] Check if `\command` subkey exists: `reg query "...\command"`2. [ ] Verify quotes are preserved in the command value3. [ ] Test with a simple path first (no spaces)4. [ ] Test with a path containing spaces5. [ ] Check Windows Event Viewer for errors6. [ ] Try running the command manually in cmd/PowerShell</debugging_checklist>---> Converted and distributed by [TomeVault](https://tomevault.io/claim/herbhall) — claim your Tome and manage your conversions.

Frequently asked questions