powershell

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

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/powershell/SKILL.md

Quality

Content

82%Weight 40%Scale 1-5

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

A lean, highly actionable skill with copy-paste-ready PowerShell throughout and a sensible install-then-reopen workflow with safety guidance. The gaps are modest: no explicit post-install validation loop and slightly project-specific content inlined where a reference file might fit better.

Suggestions

Add an explicit post-install validation step, e.g. 'After reopening PowerShell, re-run Get-Command node, npm, git -ErrorAction SilentlyContinue to confirm the tools resolved', to close the workflow's feedback loop.

Consider moving the PilotDeck-specific winget install list and pnpm filter commands into a references/ file (e.g. PILOTDECK-WINDOWS.md) and keeping only the general pattern in SKILL.md.

Tie the Safety section into the workflow more concretely by showing the read-only confirmation command to run before a destructive Remove-Item (e.g. Test-Path / Get-ChildItem on the target).

Dimension	Reasoning	Score
Conciseness	The body is dominated by executable command blocks with minimal padding and assumes Claude's competence (e.g. it never explains what PowerShell is). Minor trimming opportunities exist, such as the PilotDeck-specific pnpm install lines, which keeps it just below a 5.	4 / 5
Actionability	The guidance is fully copy-paste ready across the common cases: version checks via $PSVersionTable and per-tool '--version' calls, path inspection, the 'npm.cmd'/'pnpm.cmd' execution-policy fallback, and complete winget install commands with the Visual Studio override flags.	5 / 5
Workflow Clarity	Sequences are clear (prerequisites list, winget installs, then the explicit 'close and reopen PowerShell so PATH changes take effect' checkpoint), and the Safety section instructs confirming the target path before destructive Remove-Item usage. It falls short of a 5 because there is no explicit post-install verification step (e.g. re-running the version checks after reopening the shell).	4 / 5
Progressive Disclosure	The skill is self-contained with no bundle files and clear section organization (Shell Choice, Safe Command Patterns, PilotDeck Native Windows Notes, Safety). At roughly 73 lines, the project-specific PilotDeck notes and winget reference list could arguably live in a separate reference file, so it does not fully meet the well-split ideal.	4 / 5
	Total	17 / 20 Passed

Description

66%Weight 40%Scale 1-5

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

A specific, mostly concrete description with good natural keywords and a distinct Windows/PowerShell niche. Its main weakness is the missing 'Use when...' trigger clause, which caps completeness and slightly weakens its value for skill selection.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user is on Windows, asks for PowerShell or pwsh commands, or needs to translate a Bash snippet for a Windows environment.'

Include common synonyms and file extensions in the description such as 'pwsh', '.ps1', and 'Windows PowerShell 7' to strengthen trigger-term coverage.

Make the third capability more concrete by naming what 'troubleshoot native Windows setup' covers (e.g. 'install prerequisites with winget, fix PATH and execution-policy issues').

Dimension	Reasoning	Score
Specificity	The description lists several concrete actions ('Run safe PowerShell commands', 'translate Bash snippets', 'troubleshoot native Windows setup'), though 'troubleshoot native Windows setup' is comparatively generic. It exceeds the 1-2 concrete actions of a score-3 anchor but falls short of comprehensive coverage.	4 / 5
Completeness	The 'what' is clear (run safe commands, translate Bash snippets, troubleshoot setup), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. The Windows context only weakly implies 'when'.	3 / 5
Trigger Term Quality	'PowerShell', 'Windows', and 'Bash' are natural terms users would say, giving good keyword coverage. A few natural variations are missing, such as 'pwsh', '.ps1', or 'Windows-only', keeping it below the comprehensive synonym/extension coverage of a 5.	4 / 5
Distinctiveness Conflict Risk	PowerShell-on-Windows with Bash translation is a fairly distinct niche with clear triggers. There is minor overlap risk with general Bash/shell or WSL-related skills, so it does not reach the minimal-conflict clarity of a 5.	4 / 5
	Total	15 / 20 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: 66bfd09

Reviewed: 2 days 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.