Windows Powershell

What it does

When your agent uses it

• User asks to check system info
• Install tools on Windows
• Clean up disk space
• Set up PowerShell profile

Example prompts

• “Use the windows-powershell skill to window 11 system administration with PowerShell — system info reporting, hardware monitoring, package management…”
• “/windows-powershell”

Requirements

• Python 3
• PowerShell
• Docker
• Compatibility (from SKILL.md): opencode
• Pre-approved tools (allowed-tools): Read, Bash, Write

Workflow steps

5 steps, taken from the step headings in SKILL.md.

1. 1System health check
2. 2System cleanup
3. 3Install development tools
4. 4Set up PowerShell profile
5. 5Schedule recurring maintenance

What it can do on your machine

Read from SKILL.md and the folder at commit 4c68e5b. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves these tools, so the agent can use them without asking each time:

  • Read
  • Bash
  • Write

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Ships 3 files in scripts/ (PowerShell), which the agent can run.

  Shell commands in SKILL.md call:

  • node
  • winget

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  Hosts in commands or code, which the agent is likely to contact:

  • speedtest.url

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

• Compatibility

  opencode

  From compatibility in the SKILL.md frontmatter.

Context cost

Windows Powershell loads about 2.3k tokens when it runs, and up to ~4.5k if it reads all its reference files. Until then it costs about 136 tokens; SKILL.md has 532 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~136

When it runs · the whole SKILL.md, loaded when a task matches

~2.3k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~4.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

• NotePre-approves every shell command (allowed-tools: Bash)SKILL.md

  allowed-tools: Read, Bash, Write

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from EliasOulkadi/shokunin at commit 4c68e5b, republished under its MIT licence (© EliasOulkadi). 532 words, ~2,336 tokens.

name

windows-powershell

description

Windows 11 system administration with PowerShell — system info reporting, hardware monitoring, package management (winget/scoop), disk cleanup, performance optimization, environment configuration, PowerShell profile setup with aliases and autocomplete, and Task Scheduler automation. Use when user asks to check system info, install tools on Windows, clean up disk space, set up PowerShell profile, or automate Windows tasks. Do NOT use for Linux administration, cross-platform scripting, or network infrastructure management.

allowed-tools

Read, Bash, Write

compatibility

opencode

triggers

PowerShell, Windows, system info, winget, scoop, Chocolatey, disk cleanup, Windows optimization, environment variables, Windows profile, PowerShell profile…

negatives

Linux, macOS, bash, cross-platform, WSL, Linux administration

license

MIT

metadata.workflow

operations

metadata.audience

developers

metadata.version

3.0.0

metadata.author

shokunin

scripts/system-info.ps1

# Preview what would be cleaned
scripts/cleanup-system.ps1 -DryRun

# Clean everything
scripts/cleanup-system.ps1

# Install everything
scripts/install-tools.ps1

# Install specific categories only
scripts/install-tools.ps1 -Scope dev  # Git, Node, Python, VS Code
scripts/install-tools.ps1 -Scope tools  # 7-Zip, Windows Terminal, Oh My Posh

# Install the premium profile
Copy-Item "~\\.config\\opencode\\skills\\windows-powershell\\assets\\Microsoft.PowerShell_profile.ps1" $PROFILE

# Reload profile
. $PROFILE

# Weekly cleanup every Sunday at 9 PM
schtasks /Create /SC WEEKLY /D SUN /TN "SystemCleanup" /TR "powershell.exe -File '~\\.config\\opencode\\skills\\windows-powershell\\scripts\\cleanup-system.ps1'" /ST 21:00 /RL HIGHEST

Configuration WebServer {
    Import-DscResource -ModuleName PSDesiredStateConfiguration
    Node "localhost" {
        WindowsFeature IIS { Name = "Web-Server"; Ensure = "Present" }
        File WebContent {
            Ensure = "Present"
            SourcePath = "C:\inetpub\wwwroot"
            DestinationPath = "C:\inetpub\wwwroot"
            DependsOn = "[WindowsFeature]IIS"
        }
    }
}
WebServer -OutputPath C:\DSC
Start-DscConfiguration -Path C:\DSC -Wait -Verbose

# Create a restricted endpoint that only allows Get-Service + Restart-Service
New-PSSessionConfigurationFile -Path .\HelpDesk.pssc -SessionType RestrictedRemoteServer `
    -VisibleCmdlets @{ Name = 'Get-Service'; Parameters = @{ Name = 'Name' }},
                    @{ Name = 'Restart-Service'; Parameters = @{ Name = 'Name' }}
Register-PSSessionConfiguration -Name HelpDesk -Path .\HelpDesk.pssc -Force

# Enable on target machine (admin)
Enable-PSRemoting -Force
Set-Item WSMan:\localhost\Client\TrustedHosts -Value "192.168.1.100"

# Connect from source
$session = New-PSSession -ComputerName 192.168.1.100 -Credential (Get-Credential)
Invoke-Command -Session $session -ScriptBlock { Get-Process }
Remove-PSSession $session

# Generate self-signed certificate
$cert = New-SelfSignedCertificate -Subject "CN=PowerShell Code Signing" -Type CodeSigningCert -CertStoreLocation Cert:\CurrentUser\My

# Sign a script
Set-AuthenticodeSignature -FilePath .\script.ps1 -Certificate $cert

# Verify
Get-AuthenticodeSignature .\script.ps1

# Enforce in session
Set-ExecutionPolicy AllSigned -Scope Process

New-ModuleManifest -Path .\MyModule.psd1 -RootModule MyModule.psm1 -Author "YourName" `
    -CompanyName "Company" -Description "Module description" -PowerShellVersion "5.1" `
    -FunctionsToExport @("Get-Data","Set-Data") -RequiredModules @("Az","SqlServer")

# Pattern 1: Try/Catch/Finally with resource cleanup
try {
    $conn = New-Object System.Data.SqlClient.SqlConnection($connString)
    $conn.Open()
    # Work
} catch [System.Data.SqlClient.SqlException] {
    Write-Error "Database error: $_"
} catch {
    Write-Error "Unexpected: $_"
} finally {
    if ($conn) { $conn.Dispose() }
}

# Pattern 2: -ErrorAction with $ErrorActionPreference
Get-ChildItem -Path $path -ErrorAction Stop
# or globally
$ErrorActionPreference = "Stop"

# Pattern 3: $LASTEXITCODE for native commands
& python script.py
if ($LASTEXITCODE -ne 0) {
    throw "Python script failed with exit code $LASTEXITCODE"
}

# Pattern 4: $? for PowerShell commands
Get-Item $path -ErrorAction SilentlyContinue
if (-not $?) {
    Write-Warning "Path not found, using default"
}

© EliasOulkadi, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (scripts, references, assets) in .pack/skills/windows-powershell of EliasOulkadi/shokunin.

• SKILL.md
• assets/Microsoft.PowerShell_profile.ps1
• references/powershell-mastery.md
• scripts/cleanup-system.ps1
• scripts/install-tools.ps1
• scripts/system-info.ps1

Open the folder on GitHubat commit 4c68e5b