tommy-monitoring-dashboard_skill

This skill provides real-time zero-token Discord monitoring with auto-updating dashboards for OpenClaw, tracking activity, health, and performance.

Python

2.5k

GitHub Stars

6

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill tommy-monitoring-dashboard

_meta.json308 B
install.sh3.8 KB
package.json1.4 KB
README.md4.7 KB
SETUP.md3.9 KB
SKILL.md5.1 KB

Overview

This skill provides a zero-token real-time Discord monitoring dashboard for OpenClaw. It posts and persistently updates dashboard messages in a dedicated channel every 60–120 seconds to show activity, system health, and performance analytics. The design uses shell scripts and the OpenClaw CLI so there are no LLM token costs or runtime inference fees.

How this skill works

A background shell updater collects metrics (CPU, memory, disk, uptime, processes, cron jobs, sessions) and appends historical samples to lightweight CSV stores. An alert engine compares metrics to configurable thresholds and logs events. The updater edits persistent Discord messages via the OpenClaw message CLI so the channel shows live state without spamming new messages.

When to use it

Monitor OpenClaw deployments in production or staging with low operational cost
Track cron job execution, subagent activity, and session counts in real time
Detect resource pressure (CPU, memory, disk) and receive threshold alerts
Capture short-term performance trends and peak usage patterns
Provide a persistent team-facing dashboard inside Discord for incident response

Best practices

Configure sensible warning/critical thresholds in performance-config.json to reduce noise
Place the monitoring channel in a role-restricted area and limit who can edit messages
Keep retention_days small for high-frequency systems to limit disk usage
Ensure required tools (jq, bc, ps, top, df) and the OpenClaw message tool are available
Run the updater under a supervisor (systemd or a process manager) for resilience

Example use cases

View active subagents and running cron jobs from within your team’s Discord workspace
Receive color-coded alerts when CPU or memory crosses configured thresholds
Analyze hourly/daily performance trends without launching external dashboards
Audit recent alerts and peak usage to guide scaling or tuning decisions
Archive historical metrics for short-term forensics and capacity planning

FAQ

No. All collection, formatting, and Discord edits are shell-based and use the OpenClaw CLI, so there are no LLM token costs.

How often are updates posted?

By default messages are edited every 60 seconds; the interval can be adjusted in the updater script.

What happens to old performance data?

Data is retained based on retention_days in performance-config.json and old files are cleaned up automatically.