Skip to content
Skills Library
Programming · Building & coding

powershell-advanced-scripting

/powershell-advanced-scripting

Use this skill when building enterprise PowerShell modules, parameter validation, pipeline object processing, and error handling.

Licence
MIT
Last repository change
28.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use this skill when building enterprise PowerShell modules, parameter validation, pipeline object processing, and error handling.

Original author description

Use this skill when building enterprise PowerShell modules, parameter validation, pipeline object processing, and error handling.

How it works

  1. When to use
  2. Prerequisites
  3. Step-by-step workflow
  4. Commands / code examples
  5. Common mistakes & pitfalls
  6. Verification checklist
  7. Related skills
Original SKILL.md headings · 55 lines, 269 words
SKILL.md preview
---
name: powershell-advanced-scripting
description: Use this skill when building enterprise PowerShell modules, parameter validation, pipeline object processing, and error handling.
---
# PowerShell Advanced Scripting & Modules

## When to use
Use this skill when you need to building enterprise PowerShell modules, parameter validation, pipeline object processing, and error handling.

## Prerequisites
- Working knowledge of relevant programming language or database fundamentals.
- Access to testing environment or local runtime instance.

## Step-by-step workflow
1. **Analyze operational requirements**: Review performance boundaries, data integrity constraints, and query patterns.
2. **Design schema / interface**: Define explicit data contracts, types, or indexes supporting planned operations.
3. **Implement core routines**: Construct declarative, type-safe, or parameterized queries and functions.
4. **Validate performance**: Verify execution metrics using profilers, EXPLAIN plans, or benchmark test suites.
5. **Implement defensive controls**: Enforce timeout boundaries, connection pooling limits, and transaction safety.

## Commands / code examples
```powershell
function Invoke-BatchHealthCheck {
    [CmdletBinding()]
    param(
        [Parameter(Mandatory = $true, ValueFromPipeline = $true)]
        [string[]]$ComputerNames,
        [int]$TimeoutSeconds = 5
    )
    process {
        foreach ($computer in $ComputerNames) {
            $isReachable = Test-Connection -ComputerName $computer -Count 1 -Quiet
            [PSCustomObject]@{
                ComputerName = $computer
                Reachable    = $isReachable
                Timestamp    = (Get-Date).ToString("o")
            }
        }
    }
}
```

## Common mistakes & pitfalls
- Overlooking indexing strategies on foreign keys and frequently queried filter columns.
- Running unparameterized dynamic queries, creating severe SQL injection vulnerabilities.
- Holding open long-running database transactions during slow external network calls.

## Verification checklist
- [ ] Schema contracts and type signatures are strictly enforced.
- [ ] Queries are fully parameterized against injection vulnerabilities.
- [ ] Profiling or execution plans show optimal resource consumption.
- [ ] Error handling safely releases locks and rolls back aborted transactions.

## Related skills
- postgresql-query-optimization-explain
- sql-anti-patterns-remediation
- acid-transactions-isolation-levels
- secure-code-review-static-analysis-sast

Versions

The database has no other skills named powershell-advanced-scripting.

Database snapshot: 13.11.2026 · package version 4b321e770202 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 98powershell-conventions
    Best practices and conventions for PowerShell cmdlet development and scripting. Covers Verb-Noun naming with approved verbs, PascalCase parameter and variable naming, parameter design with validation attributes and tab completion, pipeline support via ValueFromPipeline and rich…
  • 98powershell-core
    Use when writing PowerShell scripts or automating tasks with PowerShell 7+ (the cross-platform edition). Covers cmdlet patterns, pipeline, objects vs text, modules, error handling, remoting, and differences from Windows PowerShell 5.1. USE FOR: PowerShell 7, PowerShell Core,…
  • 100powershell
    PowerShell 7+ scripting reference. Trigger on .ps1, .psm1, .psd1 files, debugging PowerShell errors, shell automation, CI/CD pipelines, or credential security. testing. Only PS 7+ — no 5.1 legacy.
  • 100powershell
    Enterprise PowerShell coding standards. Use when writing, reviewing, or generating any PowerShell code, creating PS1 scripts or functions, debugging PowerShell, or asked to help with PowerShell. Enforces best practices for structure, error handling, security, performance, and output patterns.
  • 85powershell-automation-playbooks
    PowerShell automation playbooks for the infrastructure-engineer subagent: choosing the runtime and surviving the 5.1 and 7 compatibility gap, Windows PowerShell 5.1 with the RSAT administration modules, PowerShell 7 cross-platform cloud automation, module architecture, profile…
  • 100powershell
    PowerShell cmdlet and scripting best practices based on Microsoft guidelines Triggers on: **/*.ps1,**/*.psm1

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.