playbooks

home / skills / aidotnet / moyucode / system-info

system-info skill

/skills/tools/system-info

This skill provides a concise overview of system resources including CPU, memory, disk, network, and processes.

npx playbooks add skill aidotnet/moyucode --skill system-info

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
892 B
---
name: system-info
description: 获取系统信息，包括CPU、内存、磁盘、网络和进程详情。
metadata:
  short-description: 系统信息
source:
  repository: https://github.com/giampaolo/psutil
  license: BSD-3-Clause
---

# System Info Tool

## Description
Get detailed system information including CPU, memory, disk usage, network stats, and running processes.

## Trigger
- `/sysinfo` command
- User needs system information
- User wants to check resources

## Usage

```bash
# Full system overview
python scripts/system_info.py

# CPU information
python scripts/system_info.py --cpu

# Memory usage
python scripts/system_info.py --memory

# Disk usage
python scripts/system_info.py --disk

# Running processes
python scripts/system_info.py --processes --top 10
```

## Tags
`system`, `cpu`, `memory`, `disk`, `monitor`

## Compatibility
- Codex: ✅
- Claude Code: ✅

Overview

This skill collects and reports detailed system information including CPU, memory, disk, network, and active processes. It provides quick, scriptable snapshots and focused queries for individual subsystems. Use it to audit resources, troubleshoot performance, or feed monitoring pipelines.

How this skill works

The tool runs local inspections that read OS metrics and process tables, then summarizes usage and health indicators. It can produce a full overview or targeted reports (CPU, memory, disk, network, processes) and supports options like top-N processes. Output is suitable for human review or downstream automation.

When to use it

  • You need a full snapshot of system health before or after a deployment.
  • Investigating high CPU, memory pressure, disk saturation, or network anomalies.
  • Collecting process lists and top resource consumers for diagnostics.
  • Automating regular audits for capacity planning or compliance checks.
  • Integrating lightweight checks into scripts or monitoring hooks.

Best practices

  • Run full overview only when needed; use targeted flags to reduce output.
  • Schedule regular captures during low-impact windows to establish baselines.
  • Combine top process output with timestamps and host identifiers for tracing.
  • Avoid storing sensitive command output in public logs; redact credentials.
  • Use the tool as a data source for alert rules rather than raw alerts.

Example use cases

  • Execute a full system snapshot before a major release to compare post-release metrics.
  • Run --cpu to capture per-core load and frequency when investigating slow jobs.
  • Query --memory to verify swap usage and identify memory-hungry services.
  • Use --disk to find partitions with low free space and largest files.
  • List top 10 processes with --processes --top 10 to pinpoint resource hogs.

FAQ

Can I get only specific metrics?

Yes. Use flags to request CPU, memory, disk, network, or processes individually to limit output.

Is this safe to run on production?

Yes. The tool performs read-only inspections. Follow best practices to avoid exposing sensitive output in shared logs.