PowerShell Windows Patterns

Overview

This public intake copy packages

plugins/antigravity-awesome-skills-claude/skills/powershell-windows

https://github.com/sickn33/antigravity-awesome-skills

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

ORIGIN.md

PowerShell Windows Patterns > Critical patterns and pitfalls for Windows PowerShell. ---

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: 2. Unicode/Emoji Restriction, 3. Null Check Patterns, 4. String Interpolation, 5. Error Handling, 6. File Paths, 7. Array Operations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• This skill is applicable to execute the workflow or actions described in the overview.
• Use when the request clearly matches the imported source intent: PowerShell Windows patterns. Critical pitfalls, operator syntax, error handling.
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
• Use when provenance needs to stay visible in the answer, PR, or review packet.
• Use when copied upstream references, examples, or scripts materially improve the answer.
• Use when the workflow should remain reviewable in the public intake repo before the private enhancer takes over.

Operating Table

metadata.json

ORIGIN.md

SKILL.md

SKILL.md

## Related Skills

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
2. Read the overview and provenance files before loading any copied upstream support files.
3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
5. Validate the result against the upstream expectations and the evidence you can point to in the copied files.
6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: 2. Unicode/Emoji Restriction

CRITICAL: No Unicode in Scripts

Rule: Use ASCII characters only in PowerShell scripts.

Examples

Example 1: Ask for the upstream workflow directly

Use @powershell-windows to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @powershell-windows against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @powershell-windows for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @powershell-windows using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• ❌ Wrong - ✅ Correct
• if (Test-Path "a" -or Test-Path "b") - if ((Test-Path "a") -or (Test-Path "b"))
• if (Get-Item $x -and $y -eq 5) - if ((Get-Item $x) -and ($y -eq 5))
• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
• Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
• Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.

Imported Operating Notes

Imported: 1. Operator Syntax Rules

CRITICAL: Parentheses Required

if (Test-Path "a" -or Test-Path "b")

if ((Test-Path "a") -or (Test-Path "b"))

if (Get-Item $x -and $y -eq 5)

if ((Get-Item $x) -and ($y -eq 5))

Rule: Each cmdlet call MUST be in parentheses when using logical operators.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

plugins/antigravity-awesome-skills-claude/skills/powershell-windows

metadata.json

ORIGIN.md

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @00-andruia-consultant-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @10-andruia-skill-smith-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @20-andruia-niche-intelligence-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @2d-games

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

references

references/n/a

examples

examples/n/a

scripts

scripts/n/a

agents

agents/n/a

assets

assets/n/a

Imported Reference Notes

Imported: 3. Null Check Patterns

Always Check Before Access

$array.Count -gt 0

$array -and $array.Count -gt 0

$text.Length

if ($text) { $text.Length }

Imported: 4. String Interpolation

Complex Expressions

"Value: $($obj.prop.sub)"

Pattern:

$value = $obj.prop.sub
Write-Output "Value: $value"

Imported: 5. Error Handling

ErrorActionPreference

Try/Catch Pattern

• Don't return inside try block
• Use finally for cleanup
• Return after try/catch

Imported: 6. File Paths

Windows Path Rules

C:\Users\User\file.txt

Join-Path $env:USERPROFILE "file.txt"

Join-Path $ScriptDir "data"

Rule: Use Join-Path for cross-platform safety.

Imported: 7. Array Operations

Correct Patterns

$array = @()

$array += $item

Imported: 8. JSON Operations

CRITICAL: Depth Parameter

ConvertTo-Json

ConvertTo-Json -Depth 10

Rule: Always specify

-Depth

File Operations

Imported: 9. Common Errors

Imported: 10. Script Template

# Strict mode
Set-StrictMode -Version Latest
$ErrorActionPreference = "Continue"

# Paths
$ScriptDir = Split-Path -Parent $MyInvocation.MyCommand.Path

# Main
try {
    # Logic here
    Write-Output "[OK] Done"
    exit 0
}
catch {
    Write-Warning "Error: $_"
    exit 1
}

Remember: PowerShell has unique syntax rules. Parentheses, ASCII-only, and null checks are non-negotiable.

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.