powershell-gallery-publisher

Validate, version, and publish PowerShell modules to the PowerShell Gallery.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/MartiXDev/ai-dev-strategy --skill powershell-gallery-publisher-martixdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: powershell-gallery-publisher
Source: https://github.com/MartiXDev/ai-dev-strategy/tree/main/custom/PowerShell/skills/powershell-gallery-publisher
Command: npx skills add https://github.com/MartiXDev/ai-dev-strategy --skill powershell-gallery-publisher-martixdev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires PSScriptAnalyzer.

What problem does it solve? Publishing a PowerShell module to the PowerShell Gallery involves many error-prone steps: manifest validation, PSScriptAnalyzer checks, API key management, semantic versioning, and post-publish verification. This Skill provides a complete, structured workflow so nothing is missed before a module goes public. ## Core Features & Use Cases - Pre-Publication Validation: Runs Test-ModuleManifest, checks required Gallery metadata fields (Author, Description, ProjectUri, LicenseUri, Tags), and enforces PSScriptAnalyzer with the PSGallery rule set. - API Key & Version Management: Guides secure API key storage (secure strings, environment variables, CI/CD secrets) and semantic version increments with release notes via Update-ModuleManifest. - Publish & Verify Workflow: Executes Publish-Module with WhatIf dry-run support, monitors gallery indexing, and verifies installation from a clean environment. - Use Case: You finished a module and want to share it publicly. The Skill walks you through fixing manifest errors, resolving analyzer warnings, bumping the version, publishing, and confirming the package appears on the Gallery. ## Quick Start Ask the assistant to validate and publish your module folder to the PowerShell Gallery with a minor version bump and release notes.

Frequently Asked Questions about powershell-gallery-publisher

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

FAQPage Schema
How do I publish a PowerShell module to the PowerShell Gallery?

Validate the manifest with Test-ModuleManifest, fix PSScriptAnalyzer errors, then run Publish-Module with your NuGet API key. Use the -WhatIf flag first to preview the publish before executing it for real.

How to get and store a PowerShell Gallery API key securely?

Create an API key under Account > API Keys on powershellgallery.com with a scoped glob pattern and expiration date. Store it as an encrypted secure string, an environment variable, or a CI/CD secret—never commit it to Git.

What manifest fields are required for PowerShell Gallery publishing?

The Gallery requires Author, Description, ModuleVersion, ProjectUri, LicenseUri, and Tags in the module manifest. Use Update-ModuleManifest to add missing fields before publishing.

Why does Find-Module not show my module after publishing?

Gallery indexing takes 15-30 minutes after upload and security scanning. Wait, then verify with Find-Module using the exact name and version, or check the package page directly on the Gallery website.

Can I republish the same version of a PowerShell module?

No, the Gallery rejects duplicate versions. Increment the version following semantic versioning (major for breaking changes, minor for features, patch for fixes) and publish again.

When should I not use the PowerShell Gallery for module distribution?

For internal-only modules, use file shares, private repositories, or Azure Artifacts instead. The public Gallery is intended for modules meant to be shared openly with the community.