system_info
Skill17 starsChanged 4 months agoMITView on GitHub
Get system information, check processes, disk usage, network status
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Ahmadjamil888/imostheir own version, first seen May 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Ahmadjamil888/imos★ 1same name
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 repository12 other files it gives its agents.
- app_controlSkill
- aws_opsSkill
- code_executionSkill
- desktop_automationSkill
- docker_deploySkill
- file_operationsSkill
- gitlab_apiSkill
- gitlab_pages_ciSkill
- ops_dns_regruSkill
- ops_reverse_proxySkill
- ops_tmux_remote_deploySkill
- vps_host_sshSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Use shell commands to read system state.
- Distinctive: line 104
Avoid commands that destabilize the system.
- Distinctive: line 105
Never kill processes without explicit user confirmation.
- Distinctive: line 106
Prefer short, focused commands over huge dumps.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
System information (macOS)
Use shell commands to read system state.
General
macOS version:
sw_versHostname and user:
whoami && hostnameUptime:
uptimeProcesses
List processes (truncated):
ps aux | head -20Find a process:
pgrep -fl "process_name"Top by CPU:
ps -Arco pid,pcpu,comm | head -10Disk
Overall usage:
df -hDirectory size:
du -sh /path/to/directoryMemory & CPU
Memory:
vm_stat | head -10CPU model:
sysctl -n machdep.cpu.brand_stringNetwork
IPv4 addresses:
ifconfig | grep "inet " | grep -v 127.0.0.1Connectivity:
ping -c 3 google.comBattery
pmset -g battRules
- Pipe verbose output through
head/tail. - Avoid commands that destabilize the system.
- Never kill processes without explicit user confirmation.
- Prefer short, focused commands over huge dumps.
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.