bot-status

Bot Status Skill

Generate a comprehensive operational status report for the Aivena bot, covering every subsystem.

Report Structure

Produce all sections in order. Use status icons consistently:

• ✅ healthy / running / OK
• ⚠️ degraded / warning
• ❌ down / error / missing
• ⏳ unknown / checking
• 📊 informational metric

---

1. Overview

Show:

• Bot name, version (from package.json if available)
• Current branch and git status (clean/dirty, uncommitted count)
• Uptime context: when the current pi session started (from jobs tool if available)
• Current date/time

2. Extensions

Check both extension directories for installed extensions:

• Workspace extensions: .pi/extensions/
• Global extensions: ~/.pi/agent/extensions/

ls -1 .pi/extensions/ 2>/dev/null
ls -1 ~/.pi/agent/extensions/ 2>/dev/null

For each extension found, read its package.json to get the version:

cat .pi/extensions/<name>/package.json 2>/dev/null | grep '"version"'
cat ~/.pi/agent/extensions/<name>/package.json 2>/dev/null | grep '"version"'

Report each extension with its source (workspace or global), version, and whether it's a symlink.

If an extension appears in both locations, note it — workspace takes precedence.

Format as a compact table:

Extensions (16 loaded)
  Workspace (.pi/extensions/):
    ✅ pi-calendar        0.1.0  (symlink)
    ✅ pi-channels        0.1.0  (symlink)
  Global (~/.pi/agent/extensions/):
    ✅ pi-memory           0.2.1  (symlink)
    ✅ pi-jobs             0.1.0  (symlink)
    ...

3. Webserver

Check if the pi-webserver is responding:

curl -s --connect-timeout 5 --max-time 10 -o /dev/null -w "%{http_code}" http://localhost:4110/ 2>/dev/null

Report:

• HTTP status code
• Port (from .pi/settings.json → pi-webserver.port)
• Whether autostart is enabled

Format:

Webserver
  ✅ Responding on port 4110 (HTTP 200)
  Autostart: enabled

If unreachable:

Webserver
  ❌ Not responding on port 4110