← TermalinCONTENT HISTORY
WHAT CHANGED
Update to Termalin
Snapshot Nov 6, 2026 · 00:12 UTC · version 2.1.7
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Termalin and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Answer \"how are my servers doing\", \"is everything up\", \"anything wrong with prod\" from Termalin's monitoring data. Use when the user asks about server status, load, disk, memory, uptime or alerts, before running any command on a server.",
"included_files": [],
"name": "server-health",
"skill_md_contents": "---\r\nname: server-health\r\ndescription: Answer \"how are my servers doing\", \"is everything up\", \"anything wrong with prod\" from Termalin's monitoring data. Use when the user asks about server status, load, disk, memory, uptime or alerts, before running any command on a server.\r\n---\r\n\r\nAnswer health questions from the data Termalin already collects, not by running commands.\r\n\r\n1. Call `alerts_list` first. Open alerts are the headline: say what is wrong, on which server, since when.\r\n2. Call `server_metrics` (no `host` for all servers, default 6 hours; set `hours` when the user names a period). It returns per-server CPU, load, memory, disk per mount, failed systemd units, listening ports, certificate expiry and offline state.\r\n3. If the user asks about one server, give its name or id from `hosts_list`.\r\n\r\nHow to report:\r\n\r\n- Lead with problems: offline servers, disks over 85 %, memory under 10 % free, load above the core count, failed units, certificates expiring within 14 days. If there are none, say so in one line and give the numbers in a compact table (server, CPU, load, memory, worst disk).\r\n- Compare with the previous window when the data has it: \"disk / grew 3 GB in 6 h\" matters more than the current percentage.\r\n- Metrics come from the Connector on each server; a server that reports nothing is either offline or has monitoring switched off in Termalin. Say which, do not guess.\r\n- Only after reporting, offer the next step. If the user wants to dig in, use the `incident-triage` skill or a read-only `ssh_exec` (for example `df -h`, `free -m`, `systemctl --failed`, `journalctl -p err -n 50`) — never a command that changes state.\r\n\r\nIf `server_metrics` says monitoring is off or there is no data, tell the user to enable monitoring for that server in their Termalin account (Account → Monitoring) and that alerts only work when monitoring is on.\r\n"
}SHA-256 of public snapshot: 902b69ad0b60948016e165364f34efe3c6bb94e7e49eabf28ddf523cea9bae42