powershell

Run safe PowerShell commands on Windows, translate Bash snippets, and troubleshoot native Windows setup.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is lean and highly actionable with copy-paste-ready PowerShell commands and well-organized sections suited to a simple single-purpose skill. Workflow clarity is capped at 2 because the tool-install sequence lacks an explicit validation checkpoint to confirm prerequisites after a PATH refresh.

Suggestions

Add an explicit validation step after the winget installs and PATH refresh, e.g. re-run Get-Command node, npm, git, python, rg to confirm each tool is now available before proceeding.

Note the Node.js 22 requirement explicitly in the install block (winget selects LTS which may differ) so the exact version is unambiguous.

Dimension	Reasoning	Score
Conciseness	Lean, code-first sections with no padding or explanation of concepts Claude already knows; every line is a concrete command or a tight directive.	3 / 3
Actionability	Provides fully executable, copy-paste-ready PowerShell commands (Get-Command, winget installs, npm.cmd shims) with specific examples and error-handling flags like -ErrorAction SilentlyContinue.	3 / 3
Workflow Clarity	Commands are grouped logically but the install path (winget -> close/reopen -> verify) has no explicit validation checkpoint confirming tools are available after PATH changes, capping workflow clarity at 2.	2 / 3
Progressive Disclosure	A simple, well-organized skill under 50 lines with clear sections and no external bundle files needed; per scoring notes this earns 3 for well-organized content.	3 / 3
	Total	11 / 12 Passed

Description

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinct, naming three concrete PowerShell/Windows actions with natural trigger terms. It is capped at 2 on completeness because it omits an explicit 'Use when...' trigger clause in the frontmatter description itself, relying on the body for that guidance.

Suggestions

Add an explicit 'Use when...' trigger clause to the description, e.g. 'Use when the user is on Windows or asks for PowerShell instead of Bash/WSL.', to reach completeness 3.

Consider adding common user phrasings like 'cmd' or 'Windows command line' as trigger terms to broaden natural-language coverage.

Dimension	Reasoning	Score
Specificity	Lists three concrete actions ('Run safe PowerShell commands on Windows, translate Bash snippets, and troubleshoot native Windows setup') — multiple specific concrete actions matching the score-3 anchor.	3 / 3
Completeness	Clearly answers 'what' (three actions) but lacks an explicit 'Use when...' trigger clause in the description itself; per guidelines a missing trigger caps completeness at 2.	2 / 3
Trigger Term Quality	Natural terms users would say ('PowerShell', 'Windows', 'Bash snippets', 'Windows setup') with good coverage of common phrasings; not jargon-only.	3 / 3
Distinctiveness Conflict Risk	Clear niche (PowerShell on Windows) with distinct triggers unlikely to overlap with Bash/WSL skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: OpenBMB/PilotDeck
Path: skills/powershell/SKILL.md
Commit: c88d7d1

Reviewed: about 13 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.