How do I install the Powershell Pin Audit skill?

Run npx skillmds@latest add devolutions/powershell-pin-audit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Powershell Pin Audit safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Powershell Pin Audit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Powershell Pin Audit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Powershell Pin Audit?

devolutions (@devolutions) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Powershell Pin Audit by devolutions

Name: Powershell Pin Audit
Author: devolutions

File contents

powershell pin audit

Use this skill when updating the pinned PowerShell version, reviewing a PowerShell release bump, or checking that the repository's coordinated PowerShell pins still agree.

The audit checks the primary .github/workflows/powershell-sdk.yml workflow, the secondary .github/workflows/powershell-cli.yml workflow, .gitmodules, the README "Current pins" table, and pwsh-src/PowerShell.Common.props when the submodule is available.

Prerequisites

PowerShell 7 (pwsh).
Initialize pwsh-src/ before release-bump validation if you need target-framework verification.

Usage

Run the default audit from the repository root:

pwsh .\.agents\skills\powershell-pin-audit\scripts\Test-PowerShellPins.ps1

Require the pwsh-src/ submodule and fail if PowerShell.Common.props is unavailable:

pwsh .\.agents\skills\powershell-pin-audit\scripts\Test-PowerShellPins.ps1 -RequireSubmodule

Audit a different checkout:

pwsh .\.agents\skills\powershell-pin-audit\scripts\Test-PowerShellPins.ps1 -RepositoryRoot D:\dev\pwsh-distro

Checks

POWERSHELL_VERSION, POWERSHELL_RELEASE_TAG, POWERSHELL_UPSTREAM_TAG, and POWERSHELL_SOURCE_REF are present in both PowerShell workflows.
The two workflows use the same PowerShell pin values.
POWERSHELL_RELEASE_TAG is v$POWERSHELL_VERSION.
POWERSHELL_UPSTREAM_TAG is upstream/$POWERSHELL_RELEASE_TAG.
POWERSHELL_SOURCE_REF is downstream/$POWERSHELL_RELEASE_TAG.
The CLI workflow SDK package ID, version, and revision match the SDK workflow defaults.
.gitmodules tracks the same downstream branch as POWERSHELL_SOURCE_REF.
README "Current pins" records the same upstream release, downstream source ref, upstream base tag, and target framework.
If pwsh-src/PowerShell.Common.props exists, README's target framework matches its <TargetFramework> value.

---name: powershell-pin-auditdescription: Audits coordinated PowerShell version pins across workflows, .gitmodules, README.md, and the checked-out upstream PowerShell target framework.---# powershell pin auditUse this skill when updating the pinned PowerShell version, reviewing a PowerShell release bump, or checking that the repository's coordinated PowerShell pins still agree.The audit checks the primary `.github/workflows/powershell-sdk.yml` workflow, the secondary `.github/workflows/powershell-cli.yml` workflow, `.gitmodules`, the README "Current pins" table, and `pwsh-src/PowerShell.Common.props` when the submodule is available.## Prerequisites- PowerShell 7 (`pwsh`).- Initialize `pwsh-src/` before release-bump validation if you need target-framework verification.## UsageRun the default audit from the repository root:```powershellpwsh .\.agents\skills\powershell-pin-audit\scripts\Test-PowerShellPins.ps1```Require the `pwsh-src/` submodule and fail if `PowerShell.Common.props` is unavailable:```powershellpwsh .\.agents\skills\powershell-pin-audit\scripts\Test-PowerShellPins.ps1 -RequireSubmodule```Audit a different checkout:```powershellpwsh .\.agents\skills\powershell-pin-audit\scripts\Test-PowerShellPins.ps1 -RepositoryRoot D:\dev\pwsh-distro```## Checks- `POWERSHELL_VERSION`, `POWERSHELL_RELEASE_TAG`, `POWERSHELL_UPSTREAM_TAG`, and `POWERSHELL_SOURCE_REF` are present in both PowerShell workflows.- The two workflows use the same PowerShell pin values.- `POWERSHELL_RELEASE_TAG` is `v$POWERSHELL_VERSION`.- `POWERSHELL_UPSTREAM_TAG` is `upstream/$POWERSHELL_RELEASE_TAG`.- `POWERSHELL_SOURCE_REF` is `downstream/$POWERSHELL_RELEASE_TAG`.- The CLI workflow SDK package ID, version, and revision match the SDK workflow defaults.- `.gitmodules` tracks the same downstream branch as `POWERSHELL_SOURCE_REF`.- README "Current pins" records the same upstream release, downstream source ref, upstream base tag, and target framework.- If `pwsh-src/PowerShell.Common.props` exists, README's target framework matches its `<TargetFramework>` value.

Frequently asked questions

Powershell Pin Audit