powershell-safe

Enforce ASCII-only strings and safe quoting in PowerShell content.

16|3|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/YehudaFrankel/clankbrain --skill powershell-safe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: powershell-safe
Source: https://github.com/YehudaFrankel/clankbrain/tree/main/.claude/skills/powershell-safe
Command: npx skills add https://github.com/YehudaFrankel/clankbrain --skill powershell-safe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PowerShell content often suffers from unsafe patterns: non-ASCII characters, smart quotes, unescaped variables, and fragile here-strings that break when combined with Bash. This Skill enforces safe string patterns to prevent silent syntax errors and security issues.

Core Features & Use Cases

  • ASCII-only strings: replace em dashes and smart quotes with safe alternatives.
  • Safe Bash interop: preserve variables by quoting or file-based execution when PowerShell is run through Bash.
  • Validation and guidance: detects risky string literals and provides corrective guidance for PS scripts.

Quick Start

Provide your PowerShell content and this skill will enforce safe string patterns and correct Bash interactions.

Frequently Asked Questions about powershell-safe

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent PowerShell script errors caused by smart quotes and non-ASCII characters?

Prevent PowerShell script errors by enforcing ASCII-only strings and replacing smart quotes with safe alternatives. This validation detects risky text like em dashes and emojis, providing corrective guidance to ensure robust script execution.

How do I safely quote PowerShell variables when running scripts through Bash?

Safely quote PowerShell variables in Bash by applying proper quoting or using file-based execution. This prevents unintended variable expansion and preserves variables during PowerShell and Bash interop operations.

Why does my PowerShell here-string break when executed inline via Bash?

PowerShell here-strings break in Bash due to fragile formatting and unintended variable expansion. Enforcing safe string patterns and proper quoting corrects these risky literals, ensuring robust cross-shell execution.

What is the best way to secure PowerShell scripts for Bash interop?

Secure PowerShell scripts for Bash interop by enforcing ASCII-only strings, safe quoting, and file-based execution. This approach prevents silent syntax errors and security issues caused by unescaped variables.

Do I need to manually replace emojis in PowerShell content before execution?

You do not need to manually replace emojis in PowerShell content. Safe string validation automatically detects non-ASCII characters like emojis and provides corrective guidance to replace them with safe alternatives.