Back to Skills

powershell-master

verified

Complete PowerShell expertise system across ALL platforms (Windows/Linux/macOS). PROACTIVELY activate for: (1) ANY PowerShell task (scripts/modules/cmdlets), (2) CI/CD automation (GitHub Actions/Azure DevOps/Bitbucket), (3) Cross-platform scripting, (4) Module discovery and management (PSGallery), (5) Azure/AWS/Microsoft 365 automation, (6) Script debugging and optimization, (7) Best practices and security. Provides: PowerShell 7+ features, popular module expertise (Az, Microsoft.Graph, PnP, AWS Tools), PSGallery integration, platform-specific guidance, CI/CD pipeline patterns, cmdlet syntax mastery, and production-ready scripting patterns. Ensures professional-grade, cross-platform PowerShell automation following industry standards.

View on GitHub

Marketplace

claude-plugin-marketplace

JosiahSiegel/claude-plugin-marketplace

Plugin

powershell-master

Repository

JosiahSiegel/claude-plugin-marketplace
7stars

plugins/powershell-master/skills/powershell-master/SKILL.md

Last Verified

January 20, 2026

Install Skill

Select agents to install to:

Scope:
npx add-skill https://github.com/JosiahSiegel/claude-plugin-marketplace/blob/main/plugins/powershell-master/skills/powershell-master/SKILL.md -a claude-code --skill powershell-master

Installation paths:

Claude
.claude/skills/powershell-master/
Powered by add-skill CLI

Instructions

# PowerShell Master

## ๐Ÿšจ CRITICAL GUIDELINES

### Windows File Path Requirements

**MANDATORY: Always Use Backslashes on Windows for File Paths**

When using Edit or Write tools on Windows, you MUST use backslashes (`\`) in file paths, NOT forward slashes (`/`).

**Examples:**
- โŒ WRONG: `D:/repos/project/file.tsx`
- โœ… CORRECT: `D:\repos\project\file.tsx`

This applies to:
- Edit tool file_path parameter
- Write tool file_path parameter
- All file operations on Windows systems

### Documentation Guidelines

**NEVER create new documentation files unless explicitly requested by the user.**

- **Priority**: Update existing README.md files rather than creating new documentation
- **Repository cleanliness**: Keep repository root clean - only README.md unless user requests otherwise
- **Style**: Documentation should be concise, direct, and professional - avoid AI-generated tone
- **User preference**: Only create additional .md files when user specifically asks for documentation



---

Complete PowerShell expertise across all platforms for scripting, automation, CI/CD, and cloud management.

---

## ๐ŸŽฏ When to Activate

PROACTIVELY activate for ANY PowerShell-related task:

- โœ… **PowerShell Scripts** - Creating, reviewing, optimizing any .ps1 file
- โœ… **Cmdlets & Modules** - Finding, installing, using any PowerShell modules
- โœ… **Cross-Platform** - Windows, Linux, macOS PowerShell tasks
- โœ… **CI/CD Integration** - GitHub Actions, Azure DevOps, Bitbucket Pipelines
- โœ… **Cloud Automation** - Azure (Az), AWS, Microsoft 365 (Microsoft.Graph)
- โœ… **Module Management** - PSGallery search, installation, updates
- โœ… **Script Debugging** - Troubleshooting, performance, security
- โœ… **Best Practices** - Code quality, standards, production-ready scripts

---

## ๐Ÿ“‹ PowerShell Overview

### PowerShell Versions & Platforms

**PowerShell 7+ (Recommended)**
- Cross-platform: Windows, Linux, macOS
- Open source, actively developed
- Better performance than PowerShell 5.1
- UTF-8 by def

Validation Details

Front Matter
Required Fields
Valid Name Format
Valid Description
Has Sections
Allowed Tools
Instruction Length:
27785 chars