Powershell command runner
Skill agent-shells/powershell-skills/adapters/codex/powershell-command-runner
Use whenever Codex is operating on Windows, PowerShell, or Windows shell tasks and is about to run shell commands, inspect files, invoke external CLIs, write or run .ps1 scripts, handle Windows paths, process non-ASCII output, perform filesystem operations, or debug command failures. Trigger even when the user did not explicitly mention PowerShell.From its SKILL.md
npx -y skills add agent-shells/powershell-skills --skill powershell-command-runnerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.4 KB, 647 tokens by cl100k_base, as published. Nobody here has run it
PowerShell Command Runner
Use this skill to make Windows shell execution boring and reliable.
Start Here
Read ../../../core/execution-contract.md before high-risk Windows shell work.
This adapter depends on the repo layout: keep core/ at ../../../core; standalone copies of this adapter folder are unsupported unless core is preserved at that relative path.
Classify command risk:
normal: simple read-only commands, git status, directory listings, version checks.high: external CLIs, paths with spaces or non-ASCII characters, archives, generated scripts, encoding-sensitive output.destructive: recursive delete, recursive move, broad overwrite, commands outside the current workspace.diagnostic: a command failed once and needs a changed shape.
Default Behavior
- Keep normal commands lightweight.
- Use PowerShell syntax in PowerShell sessions.
- Prefer native PowerShell file commands for file operations.
- Prefer
-LiteralPathwhen exact path handling matters. - Check external tools with
../../../core/scripts/Test-AgentCommand.ps1before relying on them in high-risk commands, or whenever availability or source is uncertain. - Check exact paths with
../../../core/scripts/Resolve-AgentPath.ps1when spaces, non-ASCII characters, or destructive operations are involved. - Classify repeated failures with
../../../core/scripts/Classify-AgentFailure.ps1. - Use
../../../core/scripts/Invoke-AgentCommand.ps1when structured stdout, stderr, exit code, timeout, cwd, or environment handling matters. Invoke-AgentCommand.ps1V0.1 only runs Application commands; do not use it for PowerShell cmdlets, functions, or aliases; use an explicit command path when env PATH is overridden.- Use
../../../core/scripts/Invoke-AgentPowerShell.ps1when structured output from an allowlisted read-only PowerShell cmdlet matters. Invoke-AgentPowerShell.ps1only accepts structured JSON specs and read-only allowlisted cmdlets; do not use it for aliases, functions, free-form scripts, unknown parameters, or destructive risk.
Pattern Routing
- Shell mismatch:
../../../core/pattern-catalog/shell-selection.md - Paths:
../../../core/pattern-catalog/path-handling.md - Quoting:
../../../core/pattern-catalog/quoting.md - Encoding:
../../../core/pattern-catalog/encoding.md - Tool discovery:
../../../core/pattern-catalog/tool-discovery.md - Parser traps:
../../../core/pattern-catalog/powershell-parser.md - File operation safety:
../../../core/pattern-catalog/file-ops-safety.md - Timeout and process handling:
../../../core/pattern-catalog/timeout-and-process.md - Repeated failure:
../../../core/pattern-catalog/failure-retry.md
Stop Rules
- Do not repeat the same failed command shape.
- After the second failed command shape, stop and report the blocker unless new evidence changes the diagnosis.
- Do not run destructive filesystem commands without resolved target validation.
- Do not use a helper script to bypass host permission or sandbox rules.
- Do not commit raw private failure logs to the corpus.
What ships with it: 1 file
287 B alongside SKILL.md
agents/
- openai.yaml287 B