What problem does it solve? Writing durable Windows automation in PowerShell often leads to fragile scripts: unsafe recursive deletes, broken paths with spaces or Chinese characters, non-idempotent config writes, and accidental dependence on legacy Windows PowerShell 5.1. This Skill provides rules and patterns for building PowerShell 7 automation that is path-safe, idempotent, and verifiable. ## Core Features & Use Cases - Path and filesystem safety: Enforces -LiteralPath usage, absolute-path containment checks before recursive move/delete, and junction/symlink target verification. - Idempotent config and process management: Guides backup-aware config writes, hidden wrappers for scheduled tasks, correct native tool invocation with $LASTEXITCODE checks, and SupportsShouldProcess dry-run guards. - Verification discipline: Requires dry-run-first validation, idempotence re-runs, exit-code and receipt checks, and reporting of changed paths, rollback locations, and the lowest truth layer verified. - Use Case: When asked to write a scheduled task that syncs files between directories on Windows, the Skill produces a hidden-wrapper PowerShell 7 script with verified target paths, structured logging, and rollback evidence instead of a one-off shell snippet. ## Quick Start Use the PowerShell Windows automation skill to write a PowerShell 7 script that safely syncs a folder and registers it as a hidden scheduled task with idempotent config and rollback evidence.
