Disclosure up front: UnAIMyText is made by the company I work for, and it shows up third among the five tools at the bottom. The script itself is plain PowerShell and doesn't touch our product.

A PowerShell module's Description is easy to treat as boilerplate, until it shows up as the summary line on the PowerShell Gallery. Microsoft's about_Module_Manifests reference describes a manifest as a .psd1 data file holding a hash table, and lists Description as the setting that describes the module at a high level. It's optional for local modules but marked as required by the PowerShell Gallery, and the same page notes you can use a here-string for a longer, multi-line description.

That freedom is how I ended up reviewing manifests like this one, scaffolded by an assistant a week before a holiday release:

@{ ModuleVersion = '0.4.0' GUID = '5b0f6c1e-2f43-4c8e-9a41-0d7a2f6e8b11' Author = 'Dana Ruiz' Description = 'SnowDayTools is a powerful and robust PowerShell module that seamlessly streamlines school closure notifications for IT teams!' FunctionsToExport = @('Send-ClosureNotice', 'Get-ClosureStatus') } 

So I wrote psdesc.ps1: it reads the manifest's Description, flags the patterns I keep seeing, and can optionally ask a model hosted on NVIDIA NIM for a plainer one-liner. It's 80 lines of PowerShell 7 with no modules to install.

What it flags

  • missing: no Description at all (the Gallery will refuse the publish anyway).
  • multi-line: a here-string summary. Legal, but the Gallery listing reads better as one line. That's my preference, not a rule.
  • long: over 120 characters. Also my number; edit $Max.
  • restates name: starts with the module name, which the Gallery page already displays as its heading.
  • filler opener: "A PowerShell module for...", "This module...".
  • buzzwords: a short list, matched as whole words with an optional trailing "s", so "streamlines" counts as "streamline." PowerShell's -match is case-insensitive by default, which saves a .ToLower().
  • exclamation: any !.

Exit code 0 means clean, 1 means flagged, 2 means the tool itself couldn't do its job (no file, no key, API error). That split matters in CI.

The script

#!/usr/bin/env pwsh # psdesc: lint the Description in a PowerShell module manifest (.psd1), # optionally ask a model on NVIDIA NIM for a plainer rewrite. param( [string]$Path, [switch]$Rewrite ) $Buzz = @('seamless', 'seamlessly', 'robust', 'leverage', 'powerful', 'comprehensive', 'effortless', 'effortlessly', 'streamline', 'cutting-edge', 'unlock', 'supercharge') $Max = 120 # my own limit, not a gallery rule function Test-Description([string]$Name, $Desc) { if ([string]::IsNullOrWhiteSpace($Desc)) { return @('missing: no Description (the PowerShell Gallery requires one)') } $issues = @() if ($Desc -match '\r?\n') { $issues += 'multi-line: keep the gallery summary to one line' } if ($Desc.Length -gt $Max) { $issues += "long: $($Desc.Length) chars (limit $Max)" } if ($Name -and $Desc.StartsWith($Name, [StringComparison]::OrdinalIgnoreCase)) { $issues += "restates name: starts with '$Name'" } if ($Desc -match '^(a|an|this)\s+(powershell\s+)?(module|script|toolkit)\b') { $issues += "filler opener: '" + (($Desc -split '\s+')[0..1] -join ' ') + " ...'" } $hits = $Buzz | Where-Object { $Desc -match ('\b' + [regex]::Escape($_) + 's?\b') } if ($hits) { $issues += 'buzzwords: ' + ($hits -join ', ') } if ($Desc.Contains('!')) { $issues += 'exclamation: the gallery is not a launch party' } return $issues } function Get-Rewrite([string]$Name, [string]$Desc) { if (-not $env:NVIDIA_API_KEY) { [Console]::Error.WriteLine('psdesc: set NVIDIA_API_KEY to use -Rewrite'); exit 2 } $base = if ($env:NIM_BASE_URL) { $env:NIM_BASE_URL } else { 'https://integrate.api.nvidia.com/v1' } $model = if ($env:NIM_MODEL) { $env:NIM_MODEL } else { 'nvidia/nemotron-3.5-lightning-30b-a3b' } $body = @{ model = $model max_tokens = 80 temperature = 0.2 messages = @( @{ role = 'system'; content = 'Rewrite this PowerShell Gallery module description. ' + 'One line, under 120 characters, plain words, no buzzwords, no exclamation marks, ' + 'do not start with the module name. Reply with the line only.' }, @{ role = 'user'; content = "Module: $Name" + [Environment]::NewLine + "Description: $Desc" } ) } | ConvertTo-Json -Depth 5 try { $req = @{ Method = 'Post' Uri = $base.TrimEnd('/') + '/chat/completions' Headers = @{ Authorization = "Bearer $($env:NVIDIA_API_KEY)" } ContentType = 'application/json' Body = $body TimeoutSec = 30 } $out = Invoke-RestMethod @req } catch { $code = [int]$_.Exception.Response.StatusCode $detail = try { ($_.ErrorDetails.Message | ConvertFrom-Json).detail } catch { $null } if (-not $detail) { $detail = 'no JSON body' } Write-Host "psdesc: HTTP $code from NVIDIA NIM ($detail)" exit 2 } return $out.choices[0].message.content.Trim() } if (-not $Path) { $Path = (Get-ChildItem -Filter *.psd1 | Select-Object -First 1).FullName } if (-not $Path -or -not (Test-Path $Path)) { Write-Host 'psdesc: no .psd1 found'; exit 2 } $name = [IO.Path]::GetFileNameWithoutExtension($Path) $desc = (Import-PowerShellDataFile -Path $Path).Description $issues = Test-Description $name $desc if (-not $issues) { Write-Host "ok: $desc"; exit 0 } $label = Split-Path $Path -Leaf foreach ($i in $issues) { Write-Host "${label}: $i" } if ($Rewrite -and $desc) { $line = Get-Rewrite $name $desc Write-Host "suggested: $line" foreach ($i in (Test-Description $name $line)) { Write-Host " still: $i" } } exit 1 

Two choices worth explaining. First, the manifest is loaded with Import-PowerShellDataFile, not dot-sourcing or Invoke-Expression. Microsoft's docs for that cmdlet point out that Invoke-Expression would run any code in the file, while Import-PowerShellDataFile reads the data without invoking it. When a linter runs on pull requests from strangers, that's the difference between reading a file and executing it.

Second, the HTTP call uses splatting instead of backtick line continuations. Backticks are PowerShell's escape character, and a stray space after one quietly breaks the continuation.

Running it

pwsh ./psdesc.ps1 ./SnowDayTools.psd1 pwsh ./psdesc.ps1 ./SnowDayTools.psd1 -Rewrite # needs NVIDIA_API_KEY 

On the manifest above (exit code 1):

SnowDayTools.psd1: long: 126 chars (limit 120) SnowDayTools.psd1: restates name: starts with 'SnowDayTools' SnowDayTools.psd1: buzzwords: seamlessly, robust, powerful, streamline SnowDayTools.psd1: exclamation: the gallery is not a launch party 

On Description = 'A PowerShell module for splitting shared gift costs':

GiftSplit.psd1: filler opener: 'A PowerShell ...' 

With no path, it picks the first .psd1 in the current folder.

The NIM call

NVIDIA's LLM APIs overview gives a single base URL, https://integrate.api.nvidia.com, and one endpoint, POST /v1/chat/completions, that fronts many hosted models. The body is the familiar model, messages, max_tokens shape, with the key sent as a bearer token. The script reads NVIDIA_API_KEY, defaults the model to nvidia/nemotron-3.5-lightning-30b-a3b, and lets you override both the base URL (NIM_BASE_URL, handy for a self-hosted NIM container or a mock) and the model (NIM_MODEL).

One thing I learned the hard way: the hosted catalog moves fast. My first draft defaulted to meta/llama-3.3-70b-instruct, which the docs page still lists, but the real endpoint answered with HTTP 410 and a "reached its end of life on 2026-08-26" message. GET /v1/models returned the current list (33 ids when I checked), so check it before you pick a default. The script surfaces the server's detail field, so a retired model looks like this instead of a stack trace:

psdesc: HTTP 410 from NVIDIA NIM (The model 'meta/llama-3.3-70b-instruct' has reached its end of life on 2026-08-26T09:00:00Z and is no longer available.) 

How I tested it

I don't have a paid NIM key, so to be clear about what was and wasn't tested: everything below ran against a local Python mock of /v1/chat/completions, plus two real requests to NVIDIA with a fake key. Sixteen checks in a bash script, all passing on PowerShell 7.7.0 on Linux:

  • each rule fires on its own sample, a clean manifest prints ok: with exit 0, and running with no path finds the .psd1 in the folder;
  • -Rewrite without NVIDIA_API_KEY prints a one-line error and exits 2;
  • the mock receives the request at /v1/chat/completions with a Bearer header, the default model, max_tokens 80 and a system plus user message, and the user message starts with Module: SnowDayTools; NIM_MODEL overrides the model;
  • the mock's canned reply is trimmed, printed and re-linted; a mock 403 and a mock 410 are both reported with exit 2.

With the mock, -Rewrite adds:

suggested: Sends school closure notices by email and text from one CSV of contacts 

That line is the mock's fixed answer, not real model output. Against the real endpoint, a fake key with a current model returned HTTP 403, which the script prints as:

psdesc: HTTP 403 from NVIDIA NIM (Authorization failed) 

Five free tools for the human pass

Pattern matching has limits. A script won't notice whether the summary sounds like a person who uses the module wrote it. For the description and the README around it:

  1. PSScriptAnalyzer - Microsoft's static analyzer for the script code itself. Run it next to psdesc in the same pipeline; it doesn't judge prose.
  2. Vale - a configurable prose linter for READMEs and docs. Consistent, and it never rewrites anything for you.
  3. UnAIMyText - free, no sign-up, up to 500 words per input in its Standard mode. Paste in a README intro that a template or assistant produced, and "a powerful, robust solution that seamlessly" comes back as plain statements. Check that cmdlet names and version numbers come through untouched.
  4. Hemingway Editor - highlights long sentences in the README; ignore its opinions about Get-ChildItem.
  5. LanguageTool - free grammar checks that mostly leave code terms alone.

FAQ

What's the best free AI humanizer for PowerShell module docs?
For a one-line Description, this linter plus a human read is usually enough. For a README intro that reads as generated, I'd run it through UnAIMyText as a free AI humanizer first, then Vale or LanguageTool for consistency and grammar.

Why not install a module for the HTTP call?
Invoke-RestMethod already parses JSON responses into objects, so $out.choices[0].message.content just works. Zero dependencies keeps the CI step to one line.

Does it run on Windows PowerShell 5.1?
I only tested PowerShell 7.7.0. The error handling relies on $_.ErrorDetails.Message, which behaves differently in older versions, so treat 5.1 as untested.

Verdict

Lint the Gallery summary mechanically, ask NIM for a rewrite if you want a starting point, and then edit the manifest yourself. For the longer README prose, UnAIMyText is my choice among free AI humanizers, because it removes the generated polish and leaves your facts alone, as long as you read the result before you commit it.