How do I install the Glances API skill?

Run npx skillmds@latest add phattbeats/glances-api in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Glances API skill do?

Glances CLI It is listed under Integrations & APIs on SkillMD.

Is Glances API safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts, makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Glances API?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Glances API free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Glances API?

phattbeats (@phattbeats) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Glances API by phattbeats — Agent Skill

Name: Glances API
Rating: 4.2 (5 reviews)
Author: phattbeats

File contents

Glances CLI

Python CLI for the Glances monitoring API on PHATT-RAID (10.0.0.100:61208). No auth, instant responses, auto-detecting output.

Why: The old approach used 5 separate bash/node scripts piped together. One CLI, same data, cleaner.

Quick Reference

glances.py overview             # Health check — alerts if anything's wrong
glances.py cpu                  # CPU usage + iowait
glances.py mem                  # RAM usage
glances.py temp                 # CPU temperature sensors
glances.py load                 # System load (1/5/15 min)
glances.py containers [--filter NAME] [--limit N]  # Docker containers by CPU
glances.py fs                   # Disk usage by mount
glances.py diskio               # Active disk I/O
glances.py network              # Active network interfaces
glances.py system               # Hostname, OS, uptime

Setup

export GLANCES_BASE_URL="http://10.0.0.100:61208/api/4"

Default hardcoded — works without env vars.

Output

Auto-detects: JSON when piped, human-readable in terminal. Force JSON with --json.

JSON envelope:

{"ok": true, "command": "cpu", "result": {...}}

Thresholds

Metric	🟡 Warning	🔴 Critical
CPU %	85	95
RAM %	80	90
Temp °C	80	90
FS %	85	95
Load 1m	10	12

Status icons in human output: 🟢 OK, 🟡 Warning, 🔴 Critical.

Workflows

Quick health check

glances.py overview

Returns CPU, memory, load, temp, container status, and any alerts.

What's eating CPU?

glances.py containers --limit 5

Containers sorted by CPU usage, highest first.

Is it hot in here?

glances.py temp

Disk space check

glances.py fs

All mounts sorted by usage %.

What's hitting the disks?

glances.py diskio

Critical Container Monitoring

overview and containers commands check for these critical services:

OpenClaw, swag, nextcloud, browserless, PlexMediaServer

If any are missing from the running list, an alert is raised.

Notes

5 second timeout per API call
Container CPU % can exceed 100% (multi-core)
diskio and network only show active interfaces (with traffic)
Temp uses AMD Tctl sensor (the one that matters for throttling)
The old scripts (glances_fetch.sh, glances_parse.mjs, etc.) still work but this CLI replaces them

---name: glances-apidescription: Glances CLI---# Glances CLIPython CLI for the Glances monitoring API on PHATT-RAID (`10.0.0.100:61208`). No auth, instant responses, auto-detecting output.**Why:** The old approach used 5 separate bash/node scripts piped together. One CLI, same data, cleaner.## Quick Reference```bashglances.py overview # Health check — alerts if anything's wrongglances.py cpu # CPU usage + iowaitglances.py mem # RAM usageglances.py temp # CPU temperature sensorsglances.py load # System load (1/5/15 min)glances.py containers [--filter NAME] [--limit N] # Docker containers by CPUglances.py fs # Disk usage by mountglances.py diskio # Active disk I/Oglances.py network # Active network interfacesglances.py system # Hostname, OS, uptime```## Setup```bashexport GLANCES_BASE_URL="http://10.0.0.100:61208/api/4"```Default hardcoded — works without env vars.## OutputAuto-detects: JSON when piped, human-readable in terminal. Force JSON with `--json`.**JSON envelope:**```json{"ok": true, "command": "cpu", "result": {...}}```## Thresholds| Metric | 🟡 Warning | 🔴 Critical ||--------|-----------|------------|| CPU % | 85 | 95 || RAM % | 80 | 90 || Temp °C | 80 | 90 || FS % | 85 | 95 || Load 1m | 10 | 12 |Status icons in human output: 🟢 OK, 🟡 Warning, 🔴 Critical.## Workflows### Quick health check```bashglances.py overview```Returns CPU, memory, load, temp, container status, and any alerts.### What's eating CPU?```bashglances.py containers --limit 5```Containers sorted by CPU usage, highest first.### Is it hot in here?```bashglances.py temp```### Disk space check```bashglances.py fs```All mounts sorted by usage %.### What's hitting the disks?```bashglances.py diskio```## Critical Container Monitoring`overview` and `containers` commands check for these critical services:- OpenClaw, swag, nextcloud, browserless, PlexMediaServerIf any are missing from the running list, an alert is raised.## Notes- 5 second timeout per API call- Container CPU % can exceed 100% (multi-core)- `diskio` and `network` only show active interfaces (with traffic)- Temp uses AMD Tctl sensor (the one that matters for throttling)- The old scripts (`glances_fetch.sh`, `glances_parse.mjs`, etc.) still work but this CLI replaces them

Frequently asked questions

Glances API