← ClaudeAtlas

powershell-expertlisted

Develop PowerShell scripts, tools, modules, and GUIs following Microsoft best practices. Use when writing PowerShell code, creating Windows Forms/WPF interfaces, working with PowerShell Gallery modules, or needing cmdlet/module recommendations. Covers script development, parameter design, pipeline handling, error management, and GUI creation patterns. Verifies module availability and cmdlet syntax against live documentation when accuracy is critical.
aiskillstore/marketplace · ★ 329 · Data & Documents · score 79
Install: claude install-skill aiskillstore/marketplace
# PowerShell Expert Develop production-quality PowerShell scripts, tools, and GUIs using Microsoft best practices and the PowerShell ecosystem. ## Quick Reference ### Script Structure ```powershell #Requires -Version 5.1 <# .SYNOPSIS Brief description. .DESCRIPTION Detailed description. .PARAMETER Name Parameter description. .EXAMPLE Example-Usage -Name 'Value' #> [CmdletBinding()] param( [Parameter(Mandatory, ValueFromPipeline)] [ValidateNotNullOrEmpty()] [string[]]$Name, [switch]$Force ) begin { # One-time setup } process { foreach ($item in $Name) { # Per-item processing } } end { # Cleanup } ``` ### Function Template ```powershell function Verb-Noun { [CmdletBinding(SupportsShouldProcess)] param( [Parameter(Mandatory, Position = 0)] [string]$Name, [Parameter(ValueFromPipelineByPropertyName)] [Alias('CN')] [string]$ComputerName = $env:COMPUTERNAME, [switch]$PassThru ) process { if ($PSCmdlet.ShouldProcess($Name, 'Action')) { # Implementation if ($PassThru) { Write-Output $result } } } } ``` ## Workflow ### 1. Script Development Follow naming and parameter conventions: - **Verb-Noun** format with approved verbs (`Get-Verb`) - **Strong typing** with validation attributes - **Pipeline support** via `ValueFromPipeline` - **-WhatIf/-Confirm** for destructive operations See [best-practices.md](referenc