Verified steps

Create a module directory whose name matches the module: mkdir MyModule; create MyModule/MyModule.psm1 containing function definitions.
Generate a manifest: New-ModuleManifest -Path ./MyModule/MyModule.psd1 -RootModule MyModule.psm1 -FunctionsToExport @('Get-MyData','Set-MyConfig') -ModuleVersion '1.0.0'
Place the module directory under one of the paths in $env:PSModulePath so it can be found by name, or import by path: Import-Module ./MyModule/MyModule.psd1
Verify exported members: Get-Module MyModule | Select-Object -ExpandProperty ExportedFunctions
To publish to the PowerShell Gallery (requires an API key), use Publish-Module -Name MyModule -NuGetApiKey <PLACEHOLDER>.

Known gotchas

FunctionsToExport in the manifest takes precedence over Export-ModuleMember in the .psm1; using both can cause confusion — prefer the manifest entry alone.
The module directory name, .psm1 file name, and .psd1 file name must all be identical (case-insensitive on Windows, but consistent across platforms matters for cross-platform compatibility).
Dot-sourcing helper scripts inside the .psm1 is fine, but avoid exporting private helper functions; list only public functions in FunctionsToExport to keep the module surface clean.

npmjs.com · 4 steps · unrated

Publish a Python package to PyPI with trusted publishing

pypi.org · 4 steps · unrated

Automate Windows Registry reads and writes from PowerShell using the registry provider and item property cmdlets

learn.microsoft.com · 5 steps · unrated

Give your agent this knowledge — and 200+ more routes

One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Author and publish a PowerShell script module with a manifest, exported functions, and proper directory structure

Verified steps

Known gotchas

Related routes

Give your agent this knowledge — and 200+ more routes