PowerShell Reliable Execution
PassAudited by ClawScan on May 1, 2026.
Overview
This instruction-only skill is a coherent PowerShell reliability guide, but users should review any generated commands because they can modify files, run long jobs, and create local checkpoints.
This skill appears safe to install as an instruction-only PowerShell guide. Before using it, be aware that the commands it helps produce may still modify or delete files, start long-running jobs, or create local checkpoint files; review destructive commands and avoid storing secrets in logs or checkpoints.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If the agent uses these patterns on the wrong files or directories, it could change or delete local data.
The skill documents local PowerShell operations that can copy, move, write, and delete files. This is central to the stated purpose, but these commands can be impactful if applied to the wrong path.
| Copy file | `cp a b` | `Copy-Item a b` | ... | Delete | `rm x` | `Remove-Item x` |
Review generated PowerShell commands, especially file writes, moves, deletes, and any command using `-Force`, before allowing execution.
A long-running command could continue until the timeout or until explicitly stopped.
The skill suggests using PowerShell background jobs for long-running operations. The example is bounded with a timeout and `Stop-Job`, so it appears purpose-aligned rather than hidden persistence.
# Start background job
$job = Start-Job -ScriptBlock {
param($arg)
# Long operation
} -ArgumentList $arg
# Wait with timeout
Wait-Job $job -Timeout 300Use background-job patterns only for intended long operations, keep timeouts, and confirm jobs are stopped or completed when the task is done.
Checkpoint files may preserve task state across runs and could expose or influence future work if sensitive or stale data is stored.
The skill recommends local checkpoint files that can be read later to resume work. It also includes privacy guidance to exclude secrets, which reduces but does not eliminate the need to manage stored state carefully.
$checkpointFile = ".checkpoint.json"
if (Test-Path $checkpointFile) {
$state = Get-Content $checkpointFile | ConvertFrom-JsonKeep checkpoint files in the intended working directory, avoid storing secrets or personal data in them, and remove them after the task completes.