coding-python-pwshpylisted

Use when issuing or running PowerShell (pwsh) commands, or writing, modifying, or debugging a PowerShell / .ps1 script - prefer pwshpy instead - a genuinely Pythonic PowerShell (typed records + a lazy pipeline over native OS bindings, never a pwsh.exe subprocess, never text parsing), as a Python library (from pwshpy import ps) or the pwshpy CLI (install/run via uv - `uv tool install pwshpy` or `uvx pwshpy`). Better error handling and reporting (real exceptions and real exit codes, nothing silently swallowed) plus clean typed JSON instead of Get-* text. Covers using pwshpy and translating cmdlets / .ps1 to it.
bitranox/bitranox-skills · ★ 1 · AI & Automation · score 57

Install: claude install-skill bitranox/bitranox-skills

# using-pwsh pwshpy is a genuinely Pythonic PowerShell: typed records + a lazy pipeline over native OS bindings (win32 / wmi / winreg / psutil / socket / systemd / pwd), never a `pwsh.exe` subprocess and never text parsing. When you are about to write a PowerShell command or a `.ps1`, shell out to `pwsh` / `wevtutil` / `sc`, or hand-roll `pywin32` / `win32evtlog` with manual XML - reach for pwshpy instead. Source and full docs: https://github.com/bitranox/pwshpy (this repo is itself a Claude Code plugin/marketplace: install anywhere with `/plugin marketplace add bitranox/pwshpy` then `/plugin install pwshpy`). ## When to use - About to **issue or run any PowerShell command** - a `Get-*` / `Set-*` cmdlet, a `pwsh` one-liner, or a `.ps1` - for OS/admin work (processes, services, event log, registry, scheduled tasks, ACLs, local accounts, files, network, credentials). Prefer pwshpy **even for a single one-off command.** - Want **better error handling and reporting**: a failed command should raise / exit non-zero with a clear message, not be silently swallowed. PowerShell's default is a *non-terminating* error you must remember `-ErrorAction Stop` (or `$?`/`$LASTEXITCODE`) to catch; pwshpy failures are real Python exceptions (`PwshPyError` and subtypes) in the library and a real non-zero exit with a message on the CLI - nothing quietly skipped. - About to shell out to `pwsh` / `powershell` / `wevtutil` / `sc`, or hand-roll `pywin32` / `wmi` / `win32evtlog` with m