Skills powershell-windows
📦

powershell-windows

Content revision r1 Safe ⚙️ External commands

Write Better Windows PowerShell

Windows PowerShell scripts often fail because of syntax, path, encoding, and null handling issues. This skill gives concise patterns for safer, more predictable scripts.

Supports: Claude Codex Code(CC)
🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "powershell-windows" from https://skillstore.io/skills/sickn33-powershell-windows.md and its manifest at https://skillstore.io/api/skills/sickn33-powershell-windows/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-powershell-windows.md Signed manifest GET /api/skills/sickn33-powershell-windows/manifest Signed lockfile GET /api/skills/sickn33-powershell-windows/lockfile

Test it

Using "powershell-windows". Review a script that combines Test-Path checks with a logical operator.

Expected outcome:

The review flags the condition as risky and recommends wrapping each path check before combining the results.

Using "powershell-windows". Improve a script that reads JSON and writes nested objects.

Expected outcome:

The response recommends raw file reads, explicit JSON depth, UTF-8 output, and clearer error handling.

Using "powershell-windows". Create a reusable Windows PowerShell script outline.

Expected outcome:

The result describes a strict-mode structure with path setup, main logic, catch handling, final cleanup, and plain ASCII status messages.

Security Audit

Safe
v4 • 7/7/2026 Open versioned report

All static findings are false positives caused by markdown examples, fenced blocks, and PowerShell terminology in SKILL.md. The skill is documentation-only and does not instruct the agent to run external commands. No evidence found for prompt injection, data exfiltration, network access, or malicious intent.

1
Files scanned
168
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (27)
SKILL.md:19 SKILL.md:20 SKILL.md:48 SKILL.md:49 SKILL.md:59 SKILL.md:62-65 SKILL.md:65-93 SKILL.md:93-94 SKILL.md:94-95 SKILL.md:95-107 SKILL.md:107-108 SKILL.md:108-109 SKILL.md:109-119 SKILL.md:119 SKILL.md:121-127 SKILL.md:127-128 SKILL.md:128-145 SKILL.md:145-163 SKILL.md:59 SKILL.md:59 SKILL.md:2 SKILL.md:3 SKILL.md:7 SKILL.md:9 SKILL.md:38 SKILL.md:145 SKILL.md:167
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-powershell-windows/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-powershell-windows/security.svg)](https://skillstore.io/skills/sickn33-powershell-windows?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-powershell-windows?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-powershell-windows/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-powershell-windows.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). powershell-windows security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-powershell-windows/audits/4

BibTeX citation

@techreport{sickn33-sickn33-powershell-windows-2026, author = {sickn33}, title = {powershell-windows security audit report (audit version 4)}, institution = {Skillstore}, year = {2026}, number = {4}, url = {https://skillstore.io/skills/sickn33-powershell-windows/audits/4}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "powershell-windows security audit report (audit version 4)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-07" url: "https://skillstore.io/skills/sickn33-powershell-windows/audits/4" identifiers: - type: other value: "skillstore:sickn33-powershell-windows:audit:4" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

Review Windows Automation Scripts

Check scripts for common syntax traps, null access, path handling, and JSON depth mistakes before use.

Write Safer PowerShell Examples

Use concise patterns when creating documentation, runbooks, or support notes for PowerShell users.

Guide Agent-Generated Scripts

Ask an AI coding assistant to follow Windows PowerShell rules while drafting or revising automation.

Try These Prompts

Check Basic Syntax 
Review my Windows PowerShell script for syntax issues, missing parentheses, Unicode output, and unsafe null access.
Improve Reliability 
Rewrite this PowerShell script using the skill patterns for paths, arrays, JSON depth, string interpolation, and error handling.
Create a Script Template 
Create a Windows PowerShell script outline for this task. Include strict mode, clear paths, try/catch handling, and ASCII-safe output.
Audit an Automation Runbook 
Audit this PowerShell runbook for reliability risks. Identify each issue, explain the impact, and recommend a safer pattern.

Best Practices

  • Wrap cmdlet calls in parentheses before combining them with logical operators.
  • Use Join-Path and explicit JSON depth for predictable file and data handling.
  • Check values for null before reading properties, counts, or string lengths.

Avoid

  • Do not use Unicode status symbols in scripts intended for broad Windows compatibility.
  • Do not assume nested objects serialize correctly without an explicit JSON depth.
  • Do not return inside try blocks when cleanup or final status handling is required.

Frequently Asked Questions

Does this skill run PowerShell commands?
No. It provides guidance and examples for writing or reviewing Windows PowerShell scripts.
Can it help with PowerShell syntax errors?
Yes. It highlights common syntax issues such as missing parentheses and unsafe property access.
Is this only for Windows PowerShell?
The guidance targets Windows PowerShell patterns and compatibility concerns.
Does it replace script testing?
No. You should still test scripts in a safe environment before production use.
Can Claude Code or Codex use this skill?
Yes. The metadata declares support for Claude, Codex, and Claude Code.
What problems does it focus on?
It focuses on operator syntax, ASCII output, null checks, paths, arrays, JSON, and error handling.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/powershell-windows

Ref

816c62b2546ddb1c6a0453e7c781b5e095117819

Maintenance freshness

7/18/2026

Usage

14 downloads · 123 views

File structure

📄 SKILL.md