- Home
- Skills
- DevOps & Cloud
- Windows PowerShell Terminal
Windows PowerShell Terminal
Generate, review, and convert safe native Windows PowerShell commands for Windows workflows.
Free
Works with the AI Agents you already use
Windows PowerShell Terminal
Example session with this skill installed
I need to find all files ending in .log in the current directory and its subfolders, search them for the word "ERROR", and save the results to a new file called summary.txt.
- Read your context and instructions
- Compiled the windows powershell terminal
Use native PowerShell to recursively search .log files, find lines containing ERROR, and save the matches to summary.txt.
$outputPath = ".\summary.txt"
Get-ChildItem -Path "." -Recurse -File -Filter "*.log" -ErrorAction SilentlyContinue |
Select-String -Pattern "ERROR" |
ForEach-Object {
"{0}:{1}: {2}" -f $_.Path, $_.LineNumber, $_.Line
} |
Set-Content -Path $outputPath -Encoding utf8
The output contains the source file path, matching line number, and matching text for each result.
On Windows PowerShell 5.1, Set-Content -Encoding utf8 writes UTF-8 with BOM. If summary.txt must be UTF-8 without BOM, use the .NET encoding pattern instead:
$utf8NoBom = New-Object System.Text.UTF8Encoding($false)
$outputPath = [System.IO.Path]::GetFullPath(".\summary.txt")
$results = Get-ChildItem -Path "." -Recurse -File -Filter "*.log" -ErrorAction SilentlyContinue |
Select-String -Pattern "ERROR" |
ForEach-Object {
"{0}:{1}: {2}" -f $_.Path, $_.LineNumber, $_.Line
}
[System.IO.File]::WriteAllLines($outputPath, $results, $utf8NoBom)
This remains fully native PowerShell and does not depend on grep, find, WSL, or Git Bash.
Connects securely to your tools. The creator never sees your data.
About this skill
Windows PowerShell Terminal is a portable Agent Skill for generating, reviewing, converting, and executing safe native Windows PowerShell commands.
It is designed for developers, Windows administrators, and AI coding-agent users who need correct PowerShell syntax instead of Linux, Bash, WSL, Git Bash, or CMD commands being used accidentally.
What it does
- Converts Bash and Linux-style terminal commands into native Windows PowerShell equivalents.
- Handles Windows PowerShell 5.1 and PowerShell 7+ syntax differences.
- Provides safe patterns for file creation, copying, moving, searching, and deletion.
- Handles Windows paths, quoting, environment variables, and native CLI arguments.
- Uses
$LASTEXITCODEand PowerShell error handling correctly for tools such as npm, Node.js, Python, Git, SSH, Docker, and other command-line programs. - Provides guidance for UTF-8, BOM-sensitive files, redirection, and output encoding.
- Avoids unsafe destructive commands by using inspection and
-WhatIfpreviews when appropriate. - Preserves the user's requested shell instead of silently switching to WSL, Bash, Linux, macOS, or CMD.
PowerShell version support
When a user explicitly says "Windows PowerShell", the skill assumes Windows PowerShell 5.1 unless version information proves otherwise.
PowerShell 7+ is also supported, including newer syntax such as && and || where appropriate.
Example use cases
- Convert
rm -rf node_modulesto a safe native PowerShell workflow. - Fix a command that works in Bash but fails in Windows PowerShell.
- Write UTF-8 without BOM from Windows PowerShell 5.1.
- Run
npm installand continue only when the command succeeds. - Search files recursively using native PowerShell.
- Safely manage environment variables for one command or session.
- Review AI-generated terminal commands for Windows compatibility.
Compatibility
The skill follows the portable SKILL.md format and is designed for AI coding agents that support Agent Skills or equivalent filesystem-based instructions.
The project is open source under the MIT License.
Targets native Windows PowerShell. It does not provide WSL, Git Bash, Linux, macOS, or CMD syntax unless needed for conversion or disambiguation. Windows PowerShell 5.1 and PowerShell 7+ differ in supported syntax and default text encoding, so version-sensitive commands may differ. Destructive operations are intentionally previewed with -WhatIf when supported and should only proceed after the target and user intent are confirmed.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
3 uses
Times used to date
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 1 day ago
- Free with an Agensi account
Permissions
This skill does not require network access or external services. It provides native PowerShell guidance through the agent's terminal. File operations and environment-variable changes are performed only when required by the user's request, and destructive operations should be explicitly scoped and previewed when supported.