Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Windows-specific patterns, security practices, and operational traps that cause silent failures.
Windows-specific patterns, security practices, and operational traps that cause silent failures.
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.
Never hardcode passwords in scripts โ use Windows Credential Manager: # Store cmdkey /generic:"MyService" /user:"admin" /pass:"secret" # Retrieve in script $cred = Get-StoredCredential -Target "MyService" For scripts, use Get-Credential and export securely: $cred | Export-Clixml -Path "cred.xml" # Encrypted to current user/machine $cred = Import-Clixml -Path "cred.xml"
Windows Defender silently quarantines downloaded scripts/executables โ check quarantine if script disappears Group Policy overrides local settings silently โ gpresult /r to see what's actually applied Antivirus real-time scanning blocks file operations intermittently โ add exclusions for build/automation folders PowerShell -ErrorAction SilentlyContinue hides problems โ use Stop and handle explicitly
Creating symlinks requires admin OR SeCreateSymbolicLinkPrivilege โ regular users fail silently Enable Developer Mode for symlinks without admin: Settings โ For Developers โ Developer Mode mklink is CMD-only, PowerShell uses New-Item -ItemType SymbolicLink
Unsigned scripts fail on restricted machines with confusing errors โ sign for production: $cert = Get-ChildItem Cert:\CurrentUser\My -CodeSigningCert Set-AuthenticodeSignature -FilePath script.ps1 -Certificate $cert AllSigned policy requires ALL scripts signed including profile.ps1
Always -WhatIf first on destructive operations โ Remove-Item -Recurse -WhatIf Start-Transcript for audit trail โ forgotten until incident investigation NTFS permissions: icacls for CLI, but inheritance rules are non-obvious โ test changes on copy first
Enable correctly: Enable-PSRemoting -Force isn't enough on workgroups Workgroup machines need TrustedHosts: Set-Item WSMan:\localhost\Client\TrustedHosts -Value "server1,server2" HTTPS remoting needs certificate setup โ HTTP sends credentials readable on network
Scripts should log to Windows Event Log for centralized monitoring: New-EventLog -LogName Application -Source "MyScript" -ErrorAction SilentlyContinue Write-EventLog -LogName Application -Source "MyScript" -EventId 1000 -Message "Started" Custom event sources require admin to create โ create during install, not runtime
Windows locks files aggressively โ test file access before operations: try { [IO.File]::OpenWrite($path).Close(); $true } catch { $false } Scheduled tasks writing to same file as user โ conflicts. Use unique temp files and atomic rename
$env:TEMP fills silently โ scripts should cleanup with try/finally: $tmp = New-TemporaryFile try { ... } finally { Remove-Item $tmp -Force } Orphaned temp files accumulate across reboots โ unlike Linux /tmp
Services run in different user context โ $env:USERPROFILE points to system profile, not user's Network access from SYSTEM account uses machine credentials โ may fail where user succeeds Mapped drives don't exist for services โ use UNC paths \\server\share
Identity, auth, scanning, governance, audit, and operational guardrails.
Largest current source with strong distribution and engagement signals.