| name | observability-dashboard-spec |
| model | sonnet |
| description | Produces an architectural specification document mapping Gateway SSE events and OTEL spans to named dashboard widgets, a data flow diagram, and an MCP App config — ready to hand to an implementation agent. Use when: "design the observability dashboard", "spec the monitoring app", "map events to widgets", "plan the agent dashboard", "extend the dashboard with new widget types". |
| license | Complete terms in LICENSE.txt |
| category | system-health |
| triggers | ["design the observability dashboard","spec the monitoring app","map events to widgets","plan the agent dashboard","extend the dashboard with new widget types"] |
| tier | 1 |
| agents | ["primary"] |
| tool_dependencies | ["file_system"] |
| inputs | [{"name":"events_to_surface","type":"string[]","description":"Gateway SSE events and OTEL spans to map to dashboard widgets","required":false}] |
| outputs | [{"name":"dashboard_spec","type":"ref","format":"cas-ref","description":"Architectural specification document mapping events to named dashboard widgets, data flow diagram, and MCP App config"}] |
Observability Dashboard Spec
Prompt-only skill (Tier 0) that produces an MCP App dashboard specification.
I. Philosophy
Observability is not logging with a UI. It is the ability to answer questions about system behavior that you did not anticipate when building the system. A well-designed dashboard does not show you every data point — it shows you the right data at the right granularity to support the three fundamental questions: What happened? Why did it happen? What should I do about it?
The Dojo Platform emits 20+ event types across three layers (SSE, OTEL spans, orchestration events). The challenge is not collecting data — it is designing views that make multi-agent DAG execution legible at a glance.
II. When to Use
- When planning the first observability MCP App for the Gateway
- When extending the dashboard with new widget types
- When the event catalog has expanded and the dashboard spec needs updating
- When designing dashboard views for specific personas (operator, developer, auditor)
III. Workflow
Step 1: Inventory the Event Catalog
Map all available data sources:
SSE Events (real-time, push):
| Event | Key Fields | Widget Candidate |
|---|
| intent_classified | intent, confidence | Intent distribution pie chart |
| provider_selected | provider, model | Model usage breakdown |
| tool_invoked | tool, arguments | Live tool call feed |
| tool_completed | tool, result, duration_ms | Tool latency histogram |
| orchestration_plan_created | plan_id, node_count, estimated_cost | DAG visualization (new plan) |
| orchestration_node_start | node_id, tool_name | DAG node state (running) |
| orchestration_node_end | node_id, state, duration_ms | DAG node state (complete/failed) |
| orchestration_replanning | reason, failed_nodes | Replanning alert |
| orchestration_complete | total_nodes, success/failed, duration_ms | DAG summary card |
| trace_span_start | trace_id, span_id, name | Trace waterfall (new span) |
| trace_span_end | duration_ms, status, metadata |
