vibe-service-health-dashboard

SkillMonitoring & ops

Queries all configured services for health status, uptime, restarts, errors, resources. Use when checking the health of running services.

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.

Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.

Then ask your AI: use the vibe-service-health-dashboard skill

What this skill tells your AI

The instructions your AI receives, as published by ash1794/vibe-engineering in plugins/vibe-engineering/skills/vibe-service-health-dashboard/SKILL.md and read by ahel’s review.

Know what's running, what's crashed, and what's about to crash.

When to Use This Skill

Checking service health after deployment
Investigating performance or availability issues
Morning standup health check
After infrastructure changes

When NOT to Use This Skill

No services running (pure library/CLI project)
Already have a monitoring dashboard (Grafana, Datadog, etc.)
Development-only local services that don't need monitoring

Steps

Discover services — Check for:
- systemd: systemctl --user list-units --type=service --state=running
- Docker: docker ps
- PM2: pm2 list
- Kubernetes: kubectl get pods
For each service, collect:
- Status (running/stopped/crashed)
- Uptime
- Last restart time and reason
- Recent error count (from logs)
- Resource usage (CPU, memory) if available
Identify issues:
- Crashed services (not running when expected)
- High-restart services (restarted >3 times recently)
- Resource-hungry processes (>80% CPU or memory)
- Error spikes (more errors than usual)
Provide remediation commands for each issue

Output Format

Service Health Dashboard

Services: X running, Y stopped, Z error Overall: HEALTHY / DEGRADED / CRITICAL

Service	Status	Uptime	Restarts	Errors (1h)	CPU	Memory
api	✓ Running	3d 4h	0	2	15%	256MB
worker	✗ Crashed	-	5	38	-	-

Issues

worker crashed — Last error: "OOM killed"
- Fix: systemctl --user restart worker or increase memory limit

Recommended Actions

[Action with command]

Signals

GitHub stars: 85
Forks: 20
Last commit: Oct 2026

Advanced

Item type: skill
Key: vibe-service-health-dashboard
Source: github.com/ash1794/vibe-engineering

github.com/ash1794/vibe-engineering