safishamsiandClaude Opus 4.8
3d19463484
The Windows skill variant had a PowerShell Step 1 but its later steps came from the shared core fragment as bash-only shell (cat-piped interpreter invocations, rm -f, find -delete). The skillgen renderer now translates the composed core to PowerShell for powershell-shell platforms (here-string interpreter invocations, Remove-Item cleanup); POSIX skills are unchanged and step / #2490 parity is enforced by a generator check. Not a regression from 0.9.35 (skill files were unchanged between 0.9.34 and 0.9.35). Thanks @tannermosher2015-debug. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
16 lines
735 B
Markdown
16 lines
735 B
Markdown
```powershell
|
|
if (-not (Test-Path graphify-out\.graphify_python)) {
|
|
$GRAPHIFY_PYTHON = $null
|
|
$graphifyCmd = Get-Command graphify -ErrorAction SilentlyContinue
|
|
if ($graphifyCmd) {
|
|
# The interpreter that owns the graphify entry point sits next to it
|
|
# (<env>\Scripts\python.exe for uv tool, pipx, and venv installs).
|
|
$py = Join-Path (Split-Path $graphifyCmd.Source) "python.exe"
|
|
if (Test-Path $py) { $GRAPHIFY_PYTHON = $py }
|
|
}
|
|
if (-not $GRAPHIFY_PYTHON) { $GRAPHIFY_PYTHON = "python" }
|
|
New-Item -ItemType Directory -Force -Path graphify-out | Out-Null
|
|
& $GRAPHIFY_PYTHON -c "import sys; open('graphify-out/.graphify_python', 'w', encoding='utf-8').write(sys.executable)"
|
|
}
|
|
```
|