Vibe Service Health Dashboard
Queries all configured services for health status — uptime, restarts, errors, resources. Use when checking the health of running services.
Install
$ agentstack add skill-ash1794-vibe-engineering-service-health-dashboard ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-ash1794-vibe-engineering-service-health-dashboard) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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
- 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 workeror increase memory limit
Recommended Actions
- [Action with command]
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ash1794
- Source: ash1794/vibe-engineering
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.