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

83%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.

The body is a lean, highly actionable pattern catalog with concrete wrong/correct tables and a full script template, assuming Claude's competence throughout. Its main gap is workflow clarity: the script template lacks explicit validation checkpoints, and no multi-step workflow with verification is laid out.

Suggestions

Add an explicit validation checkpoint to the script template (e.g. verify path existence or input shape before the main logic, and re-check after writes).

For destructive or batch file operations, include a validate → fix → retry feedback loop so workflow clarity can exceed 3.

Consider splitting the largest reference tables (e.g. Common Errors, JSON operations) into a one-level-deep reference file to enable clearer progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is table-driven with wrong/correct pairs, short rules, and a script template, assuming Claude already knows PowerShell and never explaining basic concepts — matching the score-5 anchor of lean, efficient content where every token earns its place; not score 4 because there is no padding or over-explanation to trim beyond a one-line "Remember" summary.	5 / 5
Actionability	Concrete executable snippets abound — `if ((Test-Path "a") -or (Test-Path "b"))`, `ConvertTo-Json -Depth 10`, `Join-Path $env:USERPROFILE "file.txt"`, and a full try/catch script template — covering the common cases in copy-paste-ready form per the score-5 anchor; not score 4 because the examples are complete and executable rather than having minor gaps.	5 / 5
Workflow Clarity	The script template gives a sequence (Set-StrictMode, paths, try/catch/finally, exit codes) but there are no explicit validation checkpoints, and the skill is a pattern catalog rather than a sequenced workflow with verification, fitting the score-3 anchor of steps present but checkpoints missing; not score 4 because checkpoints are absent rather than minor-gaps, and not score 2 because the template sequence is coherent.	3 / 5
Progressive Disclosure	Content is organized into ten clearly numbered, well-headed sections with easy navigation and no nested or buried references, fitting the score-4 anchor of good structure with minor gaps; not score 5 because (at ~160 lines, over the 50-line simple-skill threshold) no one-level-deep external references or content split into files is provided, and not score 3 because organization is clean rather than "could be better."	4 / 5
	Total	17 / 20 Passed

Description

61%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.

The description names a distinct niche and several relevant topic areas with strong natural trigger terms, but it omits any explicit "Use when..." trigger guidance, which caps completeness. Adding a concrete use-when clause would lift the completeness and distinctiveness scores.

Suggestions

Append an explicit trigger clause to the description, e.g. "Use when writing or debugging PowerShell scripts on Windows."

Add a common synonym or file extension (e.g. ".ps1", "cmdlet") to broaden natural trigger coverage.

Reframe topic categories ("operator syntax", "error handling") as concrete actions the skill performs to raise specificity.

Dimension	Reasoning	Score
Specificity	Quotes "PowerShell Windows patterns. Critical pitfalls, operator syntax, error handling." — names the domain plus a few concrete topic areas (operator syntax, error handling), matching the score-3 anchor of domain + 1-2 concrete items; not score 4 because the items are topic categories rather than concrete performed actions, and not score 2 because more than the domain alone is named.	3 / 5
Completeness	The description field gives a clear "what" (PowerShell Windows patterns, pitfalls, operator syntax, error handling) but contains no "Use when..." clause or equivalent trigger guidance, so per the judging guideline completeness is capped at 3; not score 4 because "when" is entirely missing rather than weakly present.	3 / 5
Trigger Term Quality	"PowerShell" and "Windows" are natural terms users would actually say, supplemented by "operator syntax" and "error handling", giving good keyword coverage per the score-4 anchor; not score 5 because synonyms and file extensions (e.g. ".ps1", "cmdlet", "scripting") are absent.	4 / 5
Distinctiveness Conflict Risk	"PowerShell Windows patterns" carves a clear, narrow niche with minimal overlap risk, fitting the score-4 anchor of mostly distinct with minor overlap; not score 5 because the description lacks the explicit "Use when..." trigger phrasing shown in the score-5 example.	4 / 5
	Total	14 / 20 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: 211561c

Reviewed: 8 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.