powershell-windows
Master PowerShell Windows Scripting Patterns
Avoid common PowerShell pitfalls that cause script failures. Learn proper operator syntax, error handling, and Windows-specific patterns for reliable automation.
下載技能 ZIP
在 Claude 中上傳
前往 設定 → 功能 → 技能 → 上傳技能
開啟並開始使用
測試它
正在使用「powershell-windows」。 Check if file exists or directory exists
預期結果:
Use: if ((Test-Path "file.txt") -or (Test-Path "folder")) - Each cmdlet must be wrapped in parentheses when using logical operators
正在使用「powershell-windows」。 Safely get array length
預期結果:
Use: if ($array -and $array.Count -gt 0) - Always verify the array exists before accessing properties
正在使用「powershell-windows」。 Convert nested object to JSON
預期結果:
Use: $data | ConvertTo-Json -Depth 10 - Always specify depth parameter for nested objects to avoid truncation
安全審計
安全Static analysis detected 34 patterns but all are false positives. The SKILL.md file is documentation only, containing PowerShell syntax examples and best practices. No executable code or security risks present. The skill is a reference guide for proper PowerShell scripting patterns on Windows.
風險因素
品質評分
你能建構什麼
DevOps Engineer Scripting
Create reliable Windows automation scripts with proper error handling and null safety for CI/CD pipelines
System Administrator Reference
Quick reference for PowerShell syntax rules and common pitfalls when maintaining legacy scripts
Developer Learning Resource
Learn PowerShell best practices and avoid common mistakes when adding Windows scripting to your toolkit
試試這些提示
What is the correct PowerShell syntax for checking if a file exists OR another condition is true?
Show me the proper try-catch-finally pattern for PowerShell scripts that need to clean up resources
How do I safely check if an array has items before accessing its Count property in PowerShell?
What is the correct way to read and write JSON files in PowerShell with nested objects?
最佳實務
- Wrap each cmdlet in parentheses when using logical operators like -or and -and
- Always check for null before accessing object properties or methods
- Use Join-Path for building file paths instead of string concatenation
- Set ErrorActionPreference appropriately for your environment (Stop for dev, Continue for production)
- Specify -Depth parameter when converting nested objects to JSON
避免
- Using unicode or emoji characters in PowerShell scripts - use ASCII markers like [OK] instead
- Accessing properties without null checks - will cause runtime errors on null values
- Using ConvertTo-Json without -Depth parameter - nested objects will be truncated
- Placing return statements inside try blocks - use finally for cleanup and return after