powershell-reliable

What This Skill Does

The powershell-reliable skill is a robust wrapper designed to standardize and stabilize PowerShell command execution within OpenClaw. It addresses the inherent volatility of shell commands on Windows by replacing unreliable bash-style syntax with proper, failure-aware PowerShell patterns. The skill enforces the use of try-catch blocks for error handling, strict encoding for file operations, and safe path construction. It is specifically built to handle long-running background tasks, preventing session timeouts, and implementing retry logic for transient failures like network fluctuations or file locks. By abstracting away the nuances of Windows-specific command parsing, it ensures that your AI agents interact with the OS in a predictable and repeatable manner.

Installation

To integrate this skill into your environment, use the OpenClaw command-line interface as follows: clawhub install openclaw/skills/skills/dalomeve/powershell-reliable

Use Cases

• Automated Deployments: Safely executing software installation scripts that require cleanup, verification, and error logging.
• System Maintenance: Managing file system cleanup, log rotation, or configuration updates that need to be persisted regardless of session state.
• Data Pipelines: Orchestrating complex PowerShell tasks that involve downloading files via web requests and processing them with native cmdlets.
• Background Task Management: Running long-duration tasks in the background with automated timeout handling and retrieval logic.

Example Prompts

1. "Use powershell-reliable to check if the C:\Logs directory exists, if not create it, then download the latest report from https://api.example.com/status and save it to that directory using UTF8 encoding."
2. "Run the system cleanup script using the powershell-reliable retry pattern, ensuring it attempts the operation 3 times before failing."
3. "Start a background job via powershell-reliable to compress the data folder, wait for 60 seconds, and return the output."

Tips & Limitations

• Always use explicit parameters: Never use shorthand aliases; always define the full parameter name to ensure script durability.
• Encoding matters: When outputting logs or generated data, strictly define -Encoding UTF8 to avoid byte-order mark corruption.
• Checkpointing: For scripts that run for more than a few minutes, always implement the checkpoint pattern provided in the documentation to allow for seamless recovery after a process interruption.
• Environment Variables: Always reference variables using the $env: prefix, as standard shell expansion often fails in non-interactive agent contexts.