Lean, step-numbered, action-first body that assumes PowerShell competence and avoids explaining basic concepts, with genuine value-adds (anti-patterns table, limitations) that Claude would not already know; not score 2 because there is no padded explanation of fundamentals, only light recurring doc-attribution phrasing.

Provides fully executable, copy-paste-ready PowerShell across install, .Tests.ps1 files, a Should matcher catalog, Mock with ParameterFilter, PesterConfiguration hashtables, and coverage/result config; not score 2 because the examples are complete and runnable rather than pseudocode or partial.

Clear linear Step 1 to Step 10 sequence with an explicit 'Verify' checkpoint (Import-Module -PassThru) and anti-patterns/limitations that serve as error-recovery guidance; not score 2 because validation is present and the destructive/batch cap does not apply to this reference-style skill.

SKILL.md is a concise 10-step overview while the heavier full CI YAML, Azure DevOps task, and Run property table are split into a real, one-level-deep, clearly-signaled references/ci-and-config.md linked twice in the body; not score 2 because references are real, shallow, and well-navigated rather than inline or deeply nested.

Lists multiple concrete actions - 'Describe/Context/It blocks, Should assertions, Mock for isolating external dependencies, BeforeAll/BeforeEach setup hooks, Invoke-Pester with PesterConfiguration for tags, code coverage, and NUnit/JUnit XML output' - matching the score-3 anchor; not score 2 because the action list is comprehensive rather than naming only 'some actions'.

Explicitly answers both what (configures Pester v5 with the listed blocks/assertions/mocks/output) and when via an explicit 'Use when the unit-under-test is a PowerShell script, function, or CLI tool invoked from pwsh' clause; not score 2 because the trigger is explicit rather than implied.

Covers natural user terms - 'PowerShell CLIs, scripts, and cmdlets', 'pwsh', 'PowerShell script, function, or CLI tool invoked from pwsh on Windows or cross-platform'; not score 2 because common variations (scripts, functions, cmdlets, pwsh) are well represented.

Clear PowerShell/Pester niche with a trigger narrowed to PowerShell/pwsh subjects, making conflict with non-PowerShell testing skills unlikely; not score 2 because the scope is sharply bounded to PowerShell tooling rather than overlapping with generic testing skills.