#I see... So skills is basically a repeat

1 messages · Page 1 of 1 (latest)

crystal fossil
#

Here's an example from yesterday:

I have a set of 5 ProxMox nodes at root@10.22.19.10 through 10.22.19.18 (even last numbers only, so skipping .11, .13, etc.).

I want to create a skill that checks all of them to make sure everything is working well. Most of it should be a script that retrieves health information from the servers, and then a bit of judgement that figures out what's important to tell me about.

It should only let me know if things are problematic, or have varied too far from the baseline.

After asking a few clarifying questions, it responded:

Done! Created the proxmox-health skill. Here's what it does:

What it found on first run:

.
.
.

Skill features:

  • Collects metrics from all 5 nodes via SSH
  • Learns baseline over time (stored in JSON, survives context compaction)
  • Only surfaces problems, not noise
  • Tracks persistent issues you might have gotten used to

Usage: Ask "check proxmox health" or "how are the servers doing?"

Files:

  • Skill: /home/claw/.npm-global/lib/node_modules/openclaw/skills/proxmox-health/
  • Baseline: baseline.json (already initialized with today's data)
  • Packaged: /home/claw/clawd/proxmox-health.skill

Want me to look into {...} issues?