CtrlK
BlogDocsLog inGet started
Tessl Logo

powershell-windows

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

54

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/powershell-windows/SKILL.md

The canonical home for this skill is powershell-windows in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

68%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, well-structured reference of concrete wrong/correct PowerShell patterns plus an executable template, but it lacks explicit validation checkpoints in its error-handling workflow and has minor redundancy.

Suggestions

Add an explicit validation/verification checkpoint to the error-handling workflow (e.g., test script output or validate JSON after ConvertFrom-Json) to lift workflow clarity above the implicit-checkpoint cap.

Remove the closing 'Remember' footer, which restates the operator/ASCII/null rules already covered in their sections.

Expand the abstract 'Store in variable first' interpolation entry into a concrete, copy-pasteable code snippet to match the actionability of the other tables.

DimensionReasoningScore

Conciseness

The body is table-driven and terse, assuming Claude's PowerShell knowledge, with only minor redundancy (the closing 'Remember' line restates the rules), so it is efficient with small trims possible.

4 / 5

Actionability

Concrete correct/wrong syntax pairs and a copy-paste script template give mostly executable guidance, though a few entries ('Store in variable first') are slightly abstract rather than fully spelled out.

4 / 5

Workflow Clarity

A try/catch/finally pattern and script template provide a rough sequence, but there are no explicit validation checkpoints or feedback loops, which the rubric flags as a cap for processes with risky operations.

3 / 5

Progressive Disclosure

Content is well-organized into ten clearly numbered, headed sections with no nested or buried references (no bundle files exist), so structure is good with only minor organization gaps.

4 / 5

Total

15

/

20

Passed

Description

53%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 is concise and names a clear, distinct niche, but it lacks an explicit 'when to use' trigger clause and offers coverage topics rather than concrete actions, which limits specificity and completeness.

Suggestions

Add a 'Use when...' clause naming natural triggers, e.g., 'Use when writing or debugging Windows PowerShell scripts, or when the user mentions PowerShell, cmdlets, or .ps1 files.'

Replace abstract coverage terms ('Critical pitfalls, operator syntax, error handling') with concrete actions like 'identifies operator-syntax pitfalls, applies null-check and JSON-depth patterns, and handles errors with try/catch.'

Include common synonyms/extensions (e.g., 'PowerShell', 'PS', '.ps1', 'cmdlet') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('PowerShell Windows patterns') and several topic areas ('Critical pitfalls, operator syntax, error handling'), but these are coverage topics rather than concrete executable actions, so it is not comprehensive.

3 / 5

Completeness

The 'what' is clear (PowerShell Windows patterns, pitfalls, operator syntax, error handling) but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

'PowerShell' and 'Windows' are natural terms a user would say, but common synonyms and variations (e.g., 'PS', 'scripting', 'cmdlet') are missing, leaving only partial keyword coverage.

3 / 5

Distinctiveness Conflict Risk

'PowerShell Windows patterns' carves a clear niche with distinct triggers and low conflict risk with other skills, though the phrasing is terse enough to leave minor overlap with generic scripting skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

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.