Analytical Ui
Use runs summary and dashboard instead of Canvas.
Skill metadata
| Source | Bundled (installed by default) |
| Path | skills/devops/analytical-ui |
| Version | 1.0.0 |
| Author | VibeOS |
| License | MIT |
| Platforms | linux, macos |
| Tags | canvas, analytics, runs, dashboard, api, open-webui |
| Related skills | vibeos-api-automation, open-webui-vibeos, cursor-capabilities-bridge, ship-web-service |
Reference: full SKILL.md
信息
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.
Analytical UI (Canvas substitute)
Cursor Canvas is an IDE-side analytical surface. In VibeOS use API Runs summary + dashboard tab + Command Center usage — do not port Cursor’s Canvas runtime.
When to Use
- User asks for “Canvas-like” metrics / run overview
- After
vibeos api run/ Open WebUI traffic, need a rollup - Ship/ops review of recent agent runs
Prerequisites
# API server
# API_SERVER_ENABLED=true + API_SERVER_KEY in ~/.vibeos/.env
# vibeos gateway running on :8642
# Dashboard tab (once)
cp -R examples/plugins/vibeos-runs-inspector ~/.vibeos/plugins/vibeos-runs-inspector
vibeos plugins enable vibeos-runs-inspector
How to Run
CLI rollup (preferred for agents):
vibeos api runs --summary
vibeos api runs --summary --json
vibeos api runs --status running --limit 20
Dashboard:
vibeos dashboard
# open tab: API Runs (/api-runs) — stats strip + filters + list/stop/start
Chat UI (not analytics): skill open-webui-vibeos.
Desktop usage charts: Command Center → Usage (existing).
Quick Reference
| Need | Surface |
|---|---|
| Counts by status | vibeos api runs --summary |
| Live table | dashboard API Runs |
| Chat frontend | Open WebUI |
| Token/cost charts | Desktop Command Center → Usage |
Procedure
- Confirm
vibeos api health. - Print
--summary; cite counts in the reply (do not invent metrics). - For deep dive, open dashboard API Runs or
vibeos api get <run_id>. - Never claim Cursor Canvas parity — say “runs summary / dashboard”.
Pitfalls
- Runs are process-local (lost on gateway restart).
- Dashboard without API key shows upstream errors — set
API_SERVER_KEY. - Do not build a second chat UI in the dashboard plugin.
Verification
vibeos api runs --summaryprintstotal=/by_status:.- Dashboard tab shows four stat tiles and a runs table.