powerskills-system
Skill49 starsChanged 8 months agoMITView on GitHub
Windows system commands and info via PowerShell. Execute shell commands, get system info (hostname, OS, uptime), list top processes, read environment variables. Use when needing to run commands, check system status, or inspect the Windows environment.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- felipemsilva/PowerSkillsword for word, first seen Mar 6, 2026
Other versions1 project uses a version of this.
Word for word · 1
- felipemsilva/PowerSkills★ 2100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- powerskillsSkill
- powerskills-browserSkill
- powerskills-desktopSkill
- powerskills-outlookSkill
- powerskills-workiqSkill
The file
Files
PowerSkills — System
Shell commands, process management, system info.
Requirements
- PowerShell 5.1+
Actions
.\powerskills.ps1 system <action> [--params]| Action | Params | Description |
exec | --command "whoami" [--timeout 30] | Run a PowerShell command |
info | System info: hostname, OS, user, domain, arch, uptime | |
processes | --limit N | Top processes by CPU (default: 20) |
env | --name PATH | Get environment variable value |
Examples
# Run a command
.\powerskills.ps1 system exec --command "Get-Process | Select -First 5"
# System info
.\powerskills.ps1 system info
# Top 10 CPU consumers
.\powerskills.ps1 system processes --limit 10
# Check an env var
.\powerskills.ps1 system env --name COMPUTERNAMEOutput Fields
info
hostname, user, domain, os, arch, ps_version, uptime_hours
processes
name, pid, cpu, mem_mb
exec
stdout, stderr, exit_code
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.