powershell-windows

PowerShell Windows patterns. Critical pitfalls, operator syntax, error handling.

Quality

72%

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 ./.agents/skills/powershell-windows/SKILL.md

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 a tight, highly actionable PowerShell patterns reference with concrete wrong/right examples and an executable template. Its main gap is the absence of explicit validation/feedback-loop checkpoints for fragile operations like JSON depth or path handling.

Suggestions

Add explicit validation checkpoints (e.g., "After ConvertFrom-Json, assert $data is not $null before accessing properties") to support a validate→fix→retry loop.

Provide a brief worked example tying the sections together into a small end-to-end script with a verify step so the workflow sequence is explicit.

Trim the closing "Remember" line and redundant "Rule:" labels where the adjacent table already conveys the rule, to tighten conciseness further.

Dimension	Reasoning	Score
Conciseness	The body is lean and table-driven, assuming Claude already knows PowerShell basics without explaining what cmdlets or the shell are; every section earns its place with minimal padding.	3 / 3
Actionability	Wrong/right syntax tables, concrete patterns (ConvertTo-Json -Depth 10, Join-Path), and a full copy-paste-ready script template give fully executable, specific guidance.	3 / 3
Workflow Clarity	Content is well organized into numbered sections and the script template shows a setup→main→catch sequence, but there are no explicit validation checkpoints or validate→fix→retry feedback loops for risky operations.	2 / 3
Progressive Disclosure	It is a single self-contained, well-sectioned reference file with no nested or multi-level references, and the pattern cheat-sheet content does not warrant splitting into separate bundle files.	3 / 3
	Total	11 / 12 Passed

Description

57%

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 names a clear niche and several relevant topic areas but stops short of listing concrete actions or embedding explicit use-when triggers in the description field itself. It is concise and specific but would benefit from explicit trigger guidance inline.

Suggestions

Add a "Use when..." trigger clause directly in the description (e.g., "Use when writing or debugging PowerShell scripts on Windows") so completeness and trigger-term quality can reach 3.

Include common natural variations such as "cmdlets", "scripts", and ".ps1" to broaden trigger-term coverage.

Reframe topic areas as concrete actions (e.g., "Write, debug, and refactor PowerShell scripts") to lift specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ("PowerShell Windows patterns") and three concrete topic areas ("Critical pitfalls, operator syntax, error handling") but describes categories the skill covers rather than concrete actions it performs.	2 / 3
Completeness	It clearly states what the skill covers (patterns, pitfalls, operator syntax, error handling) but the description field itself lacks a "Use when..." trigger clause; the when-guidance lives only in the separate when_to_use field.	2 / 3
Trigger Term Quality	"PowerShell Windows" and "error handling" are natural terms a user would say, but common variations like "scripts", "cmdlets", "Windows scripting", or ".ps1" are missing.	2 / 3
Distinctiveness Conflict Risk	"PowerShell Windows patterns" carves out a clear, narrow niche unlikely to conflict with non-shell skills, and the explicit Windows-only scoping further separates it.	3 / 3
	Total	9 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: vudovn/ag-kit
Path: .agents/skills/powershell-windows/SKILL.md
Commit: 04514f0

Reviewed: about 12 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.