AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Vibe Service Health Dashboard

skill-ash1794-vibe-engineering-service-health-dashboard · by ash1794

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

↗ Repository
— No reviews yet
0 installs
12 views
0.0% view→install

Install

$ agentstack add skill-ash1794-vibe-engineering-service-health-dashboard

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No 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.

Are you the author of Vibe Service Health Dashboard? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

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

  1. Discover services — Check for:
  • systemd: systemctl --user list-units --type=service --state=running
  • Docker: docker ps
  • PM2: pm2 list
  • Kubernetes: kubectl get pods
  1. 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
  1. 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)
  1. 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]

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

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.

More in AI & ML