Skip to main content

Vibeos Ops Health

Triage gateway, cron, and kanban health.

Skill metadata​

SourceBundled (installed by default)
Pathskills/devops/vibeos-ops-health
Version1.0.0
AuthorVibeOS
LicenseMIT
Platformslinux, macos, windows
Tagsops, gateway, cron, kanban, health
Related skillsgit-local-workflow, issue-to-pr

Reference: full SKILL.md​

info

The following is the complete skill definition that VibeOS loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.

VibeOS Ops Health

Operator playbook for the personal-AI-OS moat: gateway liveness, messaging reconnect, cron ticks, and kanban dispatcher health. Prefer these CLI checks over guessing from chat silence.

When to Use​

  • Gateway "feels stuck" or chats stop answering
  • Cron jobs missed a window
  • Kanban ready queue not spawning workers
  • After Wi-Fi / DNS blips

Prerequisites​

  • Local install with vibeos / ./scripts/vibeos on PATH
  • Read access to ~/.vibeos/logs/ (or profile home)

How to Run​

  1. Gateway + reconnect queue:
vibeos gateway status

Look for ↻ platform: reconnect in Ns and ⚠ kanban dispatcher stuck.

  1. Cron triage:
vibeos cron status
vibeos cron list

cron status now lists last-failed, delivery-error, and overdue jobs.

  1. Kanban:
vibeos kanban list --status ready
vibeos kanban stats
vibeos kanban diagnostics
  1. Logs:
vibeos logs --follow --level WARNING
# or: ~/.vibeos/logs/gateway.log

Quick Reference​

SymptomCheckLikely fix
No chat repliesgateway statusvibeos gateway restart
Platform reconnectingstatus ↻ linesWait for backoff; fix token if fatal
Cron not firingcron status ticker linesRestart gateway; inspect job errors
Ready tasks idlekanban list --status readyProfile venv/PATH/credentials
Gave-up notifymessage shows N/M failuresRaise kanban.failure_limit or fix spawn

Pitfalls​

  • Background delegate_task is process-local — use cron / terminal(notify_on_complete) for work that must survive restart.
  • Prefer no_agent cron scripts for cheap maintenance (FTS hygiene) to avoid burning model turns.
  • Do not add new core tools for ops — CLI + skills are enough.

Verification​

  • gateway status shows supervised PID and no unexpected fatals
  • cron status shows fresh heartbeat and no overdue cluster
  • Stuck kanban clears after spawn resumes (status no longer warns)