self-monitor
Skill2 starsChanged 37 days agoMITView on GitHub
Proactive self-monitoring of infrastructure, services, and health. Tracks disk/memory/load, service health, cron job status, recent errors. Auto-fixes safe issues. Triggers on: health check, heartbeat, monitor status, service status, infrastructure check.
- Deletes or force-pushes
In this repository11 other files it gives its agents.
- approval-blocked-maintenance-loopsSkill
- cost-trackerSkill
- cron-composerSkill
- cron-doctorSkill
- daily-archivistSkill
- explain-codebaseSkill
- git-guardianSkill
- narrated-motion-explainersSkill
- skill-securitySkill
- static-site-release-verificationSkill
- weekly-meta-auditSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Run during heartbeats or scheduled checks.
- Distinctive: line 156
Add to your crontab or task scheduler:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Uses the Agent Skills package format. Execution depends on the host tools and permissions; consult the frontmatter compatibility requirements where provided.
Self Monitor
Proactive self-monitoring: infrastructure, services, and health.
Usage
Run during heartbeats or scheduled checks.
1. Infrastructure Health
# Disk usage
df -h / | awk 'NR==2 {print $5}' | tr -d '%'
# Memory usage
free -m | awk 'NR==2 {printf "%.0f", $3/$2*100}'
# Load average
uptime | awk -F'load average:' '{print $2}' | awk -F',' '{print $1}'
# Top processes by memory
ps aux --sort=-%mem | head -10
# Top processes by CPU
ps aux --sort=-%cpu | head -10Thresholds:
| Metric | Warning | Critical |
| Disk | > 80% | > 90% |
| Memory | > 85% | > 95% |
| Load | > 2.0 | > 4.0 |
2. Service Health
# Check if a process is running
pgrep -f "your_process_name" >/dev/null && echo "OK" || echo "FAIL"
# Check HTTP endpoint
curl -s -o /dev/null -w "%{http_code}" http://localhost:8080/health
# Check systemd service
systemctl is-active --quiet nginx && echo "OK" || echo "FAIL"
# Check Docker container
docker ps --filter "name=mycontainer" --filter "status=running" -q | grep -q . && echo "OK" || echo "FAIL"
# Tailscale (if using)
tailscale status --json 2>/dev/null | jq -r '.Self.Online' || echo "FAIL"3. Cron Job Health
# Check recent cron executions
grep CRON /var/log/syslog | tail -20
# Count failures in last 24h
grep -c "CRON.*error\|CRON.*fail" /var/log/syslog
# List scheduled jobs
crontab -l4. Recent Errors
# Check system logs for errors
journalctl -p err --since "1 hour ago" 2>/dev/null | tail -20
# Check application logs
tail -50 ~/projects/*/logs/*.log 2>/dev/null | grep -i "error"
# Check dmesg for hardware/kernel issues
dmesg | tail -20 | grep -i "error\|fail\|warn"Quick Health Check (for heartbeat)
#!/bin/bash
# Quick health snapshot
DISK=$(df -h / | awk 'NR==2 {print $5}' | tr -d '%')
MEM=$(free -m | awk 'NR==2 {printf "%.0f", $3/$2*100}')
LOAD=$(uptime | awk -F'load average:' '{print $2}' | awk -F',' '{print $1}' | xargs)
echo "Disk: ${DISK}% | Mem: ${MEM}% | Load: ${LOAD}"
# Alert if thresholds exceeded
[ "$DISK" -gt 90 ] && echo "⚠️ Disk critical!"
[ "$MEM" -gt 95 ] && echo "⚠️ Memory critical!"Proactive Actions
When issues detected:
| Issue | Auto-Action | Alert? |
| Disk > 90% | Clean temp files, old logs | Yes |
| Key process down | Attempt restart | Yes |
| Cron 3+ failures | Generate report | Yes |
| Memory > 95% | List top processes | Yes |
Auto-fixable (safe):
# Clean old logs (> 7 days)
find /var/log -name "*.log" -mtime +7 -delete 2>/dev/null
find ~/.cache -type f -mtime +7 -delete 2>/dev/null
# Clean temp files
rm -f /tmp/agent-temp-* 2>/dev/null
rm -rf ~/.cache/pip 2>/dev/nullReport Format
## 🔍 Self-Monitor Report - [TIME]
### Health Summary
| Metric | Value | Status |
|--------|-------|--------|
| Disk | XX% | ✅/⚠️/🔴 |
| Memory | XX% | ✅/⚠️/🔴 |
| Load | X.X | ✅/⚠️/🔴 |
| Services | X/Y up | ✅/⚠️ |
### Issues Found
- [Issue 1]: [Action taken or recommended]
### Top Resource Consumers
| Process | CPU% | MEM% |
|---------|------|------|
| ... | ... | ... |Integration with Scheduled Tasks
Add to your crontab or task scheduler:
# Run health check every 30 minutes
*/30 * * * * /path/to/health-check.sh >> /var/log/health-check.log 2>&1Or run manually as part of your workflow:
./health-check.shDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

