Skip to content
cccskills
FreePublished on GitHub

vibe-service-health-dashboard

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

The English summary is being prepared. Showing the original description.

Works withKubernetes

Run score Not tested

See how to install

Files included (1)

  • SKILL.md1.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

ServiceStatusUptimeRestartsErrors (1h)CPUMemory
api✓ Running3d 4h0215%256MB
worker✗ Crashed-538--

Issues

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

Recommended Actions

  1. [Action with command]

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Validates completed work against defined acceptance criteria. Use after completing a task that has specific success criteria defined in issues, specs, or task descriptions.

The English summary is being prepared. Showing the original description.

ash1794/vibe-engineering165Updated Oct 8, 2026

Generates edge case, failure mode, and spec-driven test cases. Covers boundary values, nil inputs, concurrency, resource exhaustion, malformed data, and requirement-linked traceability tests. Use after happy-path tests exist and before claiming coverage is complete, when requirements lack tests, or before a security review.

The English summary is being prepared. Showing the original description.

ash1794/vibe-engineering165Updated Oct 8, 2026

Catches shortcuts and reward hacking — weakening or deleting tests to make them pass, hard-coding expected outputs, silently dropping requirements, or claiming work is done without running it. Use before declaring a task complete and whenever a test or requirement feels like it's in the way.

The English summary is being prepared. Showing the original description.

ash1794/vibe-engineering165Updated Oct 8, 2026

Safely integrates commits from parallel agent branches using sequential cherry-pick. Use after parallel work completes in isolated branches or worktrees.

The English summary is being prepared. Showing the original description.

ash1794/vibe-engineering165Updated Oct 8, 2026

Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering. Use when writing tests that involve goroutines, async operations, or shared mutable state.

The English summary is being prepared. Showing the original description.

ash1794/vibe-engineering165Updated Oct 8, 2026

Enforces tiered test coverage standards with three dimensions — line coverage by tier, spec-to-test traceability, and spec-to-code implementation mapping. Use before claiming code is complete.

The English summary is being prepared. Showing the original description.

ash1794/vibe-engineering165Updated Oct 8, 2026

See all skills by ash1794

Report a problem with this skill