Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Chain PowerShell commands safely without &&. Use try/catch, ErrorAction, and proper sequencing for reliable Windows execution.
Chain PowerShell commands safely without &&. Use try/catch, ErrorAction, and proper sequencing for reliable Windows execution.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Chain commands reliably on Windows PowerShell. No && anti-patterns.
PowerShell differs from bash: && does NOT work for command chaining Parameter parsing is case-insensitive but strict Errors continue by default (no fail-fast) Path separators vary (\ vs /)
Wrong: mkdir test && cd test && echo done Right: $ErrorActionPreference = 'Stop' try { New-Item -ItemType Directory -Path test -Force Set-Location test Write-Host 'done' } catch { Write-Error "Failed at step: $_" exit 1 }
# If-then pattern if (Test-Path $file) { Remove-Item $file Write-Host "Deleted" } else { Write-Warning "File not found" } # Pipeline with error handling Get-Process | Where-Object CPU -GT 100 | Stop-Process -WhatIf
$params = @{ Path = $filePath Encoding = 'UTF8' Force = $true } Set-Content @params
CriteriaVerificationNo && in scriptsSelect-String '&&' *.ps1 returns nothingErrorAction setSelect-String 'ErrorAction' *.ps1 matchestry/catch present`Select-String 'tryPaths use Join-PathSelect-String 'Join-Path' *.ps1 matches
No hardcoded credentials Use [SecureString] for passwords Environment variables via $env:VAR
Use when: Writing any PowerShell script Chaining 2+ commands Executing file operations Chain safely. Fail explicitly.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.