What is powershell-windows?

Perfect for Windows Administration Agents needing advanced scripting and automation capabilities with PowerShell powershell-windows is a set of critical patterns and pitfalls for Windows PowerShell, focusing on operator syntax rules and Unicode restrictions.

How do I install powershell-windows?

Run the command: npx killer-skills add Nickzhan1001/AI-tools/powershell-windows. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for powershell-windows?

Key use cases include: Automating Windows system administration tasks using optimized PowerShell scripts, Debugging complex PowerShell scripts with logical operator syntax issues, Generating reports on system configurations and file structures using Get-Item and Test-Path cmdlets.

Which IDEs are compatible with powershell-windows?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for powershell-windows?

Requires Windows operating system. PowerShell version compatibility required. Parentheses required for cmdlet calls with logical operators.

powershell-windows

Install powershell-windows, an AI agent skill for AI agent workflows and automation. Works with Claude Code, Cursor, and Windsurf with one-command setup.

SKILL.md

Readonly

PowerShell Windows Patterns

Name: powershell-windows
Availability: InStock
Author: Nickzhan1001

Critical patterns and pitfalls for Windows PowerShell.

1. Operator Syntax Rules

CRITICAL: Parentheses Required

❌ Wrong	✅ Correct
`if (Test-Path "a" -or Test-Path "b")`	`if ((Test-Path "a") -or (Test-Path "b"))`
`if (Get-Item $x -and $y -eq 5)`	`if ((Get-Item $x) -and ($y -eq 5))`

Rule: Each cmdlet call MUST be in parentheses when using logical operators.

2. Unicode/Emoji Restriction

CRITICAL: No Unicode in Scripts

Purpose	❌ Don't Use	✅ Use
Success	✅ ✓	[OK] [+]
Error	❌ ✗ 🔴	[!] [X]
Warning	⚠️ 🟡	[*] [WARN]
Info	ℹ️ 🔵	[i] [INFO]
Progress	⏳	[...]

Rule: Use ASCII characters only in PowerShell scripts.

3. Null Check Patterns

Always Check Before Access

❌ Wrong	✅ Correct
`$array.Count -gt 0`	`$array -and $array.Count -gt 0`
`$text.Length`	`if ($text) { $text.Length }`

4. String Interpolation

Complex Expressions

❌ Wrong	✅ Correct
`"Value: $($obj.prop.sub)"`	Store in variable first

Pattern:

$value = $obj.prop.sub
Write-Output "Value: $value"

5. Error Handling

ErrorActionPreference

Value	Use
Stop	Development (fail fast)
Continue	Production scripts
SilentlyContinue	When errors expected

Try/Catch Pattern

Don't return inside try block
Use finally for cleanup
Return after try/catch

6. File Paths

Windows Path Rules

Pattern	Use
Literal path	`C:\Users\User\file.txt`
Variable path	`Join-Path $env:USERPROFILE "file.txt"`
Relative	`Join-Path $ScriptDir "data"`

Rule: Use Join-Path for cross-platform safety.

7. Array Operations

Correct Patterns

Operation	Syntax
Empty array	`$array = @()`
Add item	`$array += $item`
ArrayList add	`$list.Add($item)

8. JSON Operations

CRITICAL: Depth Parameter

❌ Wrong	✅ Correct
`ConvertTo-Json`	`ConvertTo-Json -Depth 10`

Rule: Always specify -Depth for nested objects.

File Operations

Operation	Pattern
Read	`Get-Content "file.json" -Raw
Write	`$data

9. Common Errors

Error Message	Cause	Fix
"parameter 'or'"	Missing parentheses	Wrap cmdlets in ()
"Unexpected token"	Unicode character	Use ASCII only
"Cannot find property"	Null object	Check null first
"Cannot convert"	Type mismatch	Use .ToString()

10. Script Template

powershell
1# Strict mode
2Set-StrictMode -Version Latest
3$ErrorActionPreference = "Continue"
4
5# Paths
6$ScriptDir = Split-Path -Parent $MyInvocation.MyCommand.Path
7
8# Main
9try {
10    # Logic here
11    Write-Output "[OK] Done"
12    exit 0
13}
14catch {
15    Write-Warning "Error: $_"
16    exit 1
17}

Remember: PowerShell has unique syntax rules. Parentheses, ASCII-only, and null checks are non-negotiable.

powershell-windows — powershell-windows install and setup powershell-windows, AI-tools, community, powershell-windows install and setup, ide skills, Claude Code, Cursor, Windsurf

About this Skill

Features

# Core Topics

Agent Capability Analysis

Ideal Agent Persona

Core Value

↓ Capabilities Granted for powershell-windows

! Prerequisites & Limits

Browser Sandbox Environment

⚡️ Ready to unleash?