ReddRadar
Agent skill
health-check
System health check dispatched by the activity monitor via Control queue. Checks PM2 services, disk space, and memory usage. Use when receiving a control message containing "health-check".
Install this agent skill to your Project
npx add-skill https://github.com/zylos-ai/zylos-core/tree/main/skills/health-check
SKILL.md
System Health Check
Periodic system health check delivered via the C4 Control queue.
When to Use
- Receiving a control message with "health-check" in the content
- The activity monitor enqueues this automatically at regular intervals
Steps
1. Check PM2 Services
pm2 jlist
Parse the JSON output. Every service should have status: "online".
Record which services are stopped or errored.
2. Check Disk Space
df -h / /home 2>/dev/null || df -h /
Thresholds:
- OK: < 80% used
- Warning: 80-90% used
- Critical: > 90% used
3. Check Memory
free -m
Thresholds:
- OK: < 80% used
- Warning: 80-90% used
- Critical: > 90% used (or swap > 50% used)
4. Report Results
If all checks pass, log to ~/zylos/logs/health.log:
[YYYY-MM-DD HH:MM:SS] Health Check: PM2 X/X online, Disk XX%, Memory XX% - ALL OK
If any issues found, notify whoever is most likely to help:
- Check your memory files for a designated owner or ops person
- If none designated, notify the person you normally work with most
- Use
c4-send.jswith the appropriate channel and endpoint to send the alert
Issue Resolution
| Issue | Action |
|---|---|
| PM2 service stopped | pm2 restart <service> and report |
| High disk usage | Check logs directories, report findings |
| High memory / swap | Report findings, check for runaway processes |
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
zylos-ai/zylos-core
web-console
Built-in web interface for communicating with Claude without external services. Use when setting up or configuring the web console channel, or troubleshooting browser-based access.
zylos-ai/zylos-core
component-management
Guidelines for managing zylos components via CLI and C4 channels. Use when installing, upgrading, or uninstalling components, or when user asks about available components.
zylos-ai/zylos-core
restart-claude
Use when the user asks to restart Claude Code, or after changing settings/hooks/keybindings.
zylos-ai/zylos-core
comm-bridge
C4 communication bridge — central gateway for ALL external communication (Telegram, Lark, etc.). Use when replying to users via the "reply via" path, sending proactive messages to external channels, querying recent conversations or checkpoint status (prefer c4-db.js CLI; sqlite3 OK for unsupported queries), fetching conversation history for Memory Sync, or creating checkpoints after sync. Incoming messages are queued by channel bots and delivered to Claude via a PM2 dispatcher daemon. Session-start hooks automatically provide conversation context and can trigger Memory Sync when unsummarized conversations exceed the configured threshold.
zylos-ai/zylos-core
new-session
Start a new session when context is high. Claude uses /clear, Codex uses /exit. Use when context is high or when a fresh session is needed.
zylos-ai/zylos-core
http
Caddy-based web server providing web console hosting, file sharing, and health check endpoints. Use when configuring HTTP access, setting up file sharing, or troubleshooting web connectivity.
Didn't find tool you were looking for?