ash1794/vibe-engineering / plugins/vibe-engineering/skills/vibe-service-health-dashboard
vibe-service-health-dashboard
VerifiedQueries all configured services for health status — uptime, restarts, errors, resources. Use when checking the health of running services.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.9 KB |
SKILL.md
View on GitHub---
name: vibe-service-health-dashboard
description: Queries all configured services for health status — uptime, restarts, errors, resources. Use when checking the health of running services.
user-invocable: true
---
# vibe-service-health-dashboard
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
1. **Discover services** — Check for:
- systemd: `systemctl --user list-units --type=service --state=running`
- Docker: `docker ps`
- PM2: `pm2 list`
- Kubernetes: `kubectl get pods`
2. **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
3. **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)
4. **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
1. **worker** crashed — Last error: "OOM killed"
- Fix: `systemctl --user restart worker` or increase memory limit
### Recommended Actions
1. [Action with command]
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |