powershell-windows
PowerShell Windows patterns. Critical pitfalls, operator syntax, error handling.
71
60%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent/skills/powershell-windows/SKILL.mdQuality
Discovery
32%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 identifies the technology domain (PowerShell on Windows) but reads more like a topic list than an actionable skill description. It lacks concrete verbs describing what actions the skill enables and completely omits trigger guidance for when Claude should use it. The description would benefit from explicit actions and a 'Use when...' clause.
Suggestions
Add a 'Use when...' clause specifying triggers like 'Use when writing PowerShell scripts, debugging Windows automation, or when user mentions .ps1 files, cmdlets, or Windows scripting'
Replace abstract nouns with concrete actions: 'Writes PowerShell scripts, handles Windows-specific syntax, implements try/catch error handling, avoids common pitfalls'
Include more natural trigger terms users would say: 'ps1', 'cmdlet', 'Windows script', 'PowerShell command', 'batch automation'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (PowerShell Windows) and mentions some areas (operator syntax, error handling, pitfalls), but uses abstract nouns rather than concrete actions. No verbs describing what the skill actually does. | 2 / 3 |
Completeness | Partially addresses 'what' through topic areas but lacks any 'when' clause or explicit trigger guidance. No 'Use when...' statement to indicate when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | 'PowerShell' and 'Windows' are natural keywords users would say, but missing common variations like 'ps1', 'cmdlet', 'script', or specific error handling terms users might mention. | 2 / 3 |
Distinctiveness Conflict Risk | 'PowerShell Windows' provides some specificity that distinguishes from general scripting skills, but 'patterns' and 'error handling' are generic enough to potentially overlap with other coding or scripting skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality reference skill that efficiently documents PowerShell pitfalls using tables and concrete examples. The wrong/correct pattern comparisons are particularly effective. Minor weakness in the error handling section where guidance is slightly abstract ('Don't return inside try block') without showing the correct alternative pattern.
Suggestions
Expand the Try/Catch Pattern section with a concrete code example showing the correct pattern (variable assignment in try, return after catch) rather than just bullet points
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Uses tables for quick reference, no unnecessary explanations of what PowerShell is or how it works. Every section delivers actionable patterns without padding. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready patterns with clear wrong/correct comparisons. The script template is executable, and specific syntax patterns are shown rather than described abstractly. | 3 / 3 |
Workflow Clarity | The script template shows a basic try/catch pattern, but the error handling section lacks explicit validation checkpoints. For a pitfalls/patterns reference, the single-action guidance is clear, but the try/catch guidance ('Don't return inside try block') is vague without showing the correct pattern. | 2 / 3 |
Progressive Disclosure | Well-organized with numbered sections, clear headers, and appropriate use of tables for quick scanning. For a reference-style skill under 100 lines, the structure is excellent with no need for external file references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- Repository
- lchenrique/politron-ide
- Commit
7114206
- 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.