dashboard-status
The dashboard-status skill performs a health check on the Claude Code Agent Monitor system by querying multiple API endpoints to report server connectivity, session counts, event ingestion, hook configuration, and data freshness. Use this skill to quickly verify that the monitoring dashboard is running properly and receiving data from configured Claude Code hooks.
git clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-Monitor /tmp/dashboard-status && cp -r /tmp/dashboard-status/plugins/ccam-dashboard/skills/dashboard-status ~/.claude/skills/dashboard-statusSKILL.md
# Dashboard Status
Quick status check on the Claude Code Agent Monitor dashboard.
## Input
The user provides: **$ARGUMENTS**
Options: empty (default: full status), "quick" (API only), "verbose" (include endpoint details).
## Data Sources
| Endpoint | Returns |
|----------|---------|
| `GET /api/health` | HTTP 200 if API is running |
| `GET /api/stats` | `{ total_sessions, active_sessions, active_agents, total_agents, total_events, events_today, ws_connections, agents_by_status, sessions_by_status }` |
| `GET /api/settings/info` | Dashboard configuration: version, port, data paths |
| `GET /api/events?limit=1` | Most recent event (for freshness check) |
## Status Report
### 1. API Server
- Reachable at `http://localhost:4820`? Response time?
- If unreachable: suggest `npm start` from the project directory
### 2. System Counts
From `/api/stats`:
- Total sessions tracked (`total_sessions`)
- Active agents currently running (`active_agents`)
- Total events ingested (`total_events`)
- Events today (`events_today`)
- WebSocket connections (`ws_connections`)
### 3. Data Freshness
From latest event:
- Time since last event ingested
- If >1 hour: warn about possible hook disconnect
### 4. Hook Status
Check `~/.claude/settings.json` for configured hooks:
- Expected: PreToolUse, PostToolUse, Stop, SubagentStop, Notification, SessionStart, SessionEnd
- Report which hooks are present vs missing
### 5. Dashboard Info
From `/api/settings/info`:
- Dashboard version
- Database path and size
- Configured port
## Output Format
Compact status card:
```
╔══════════════════════════════════════╗
║ AGENT MONITOR STATUS ║
╠══════════════════════════════════════╣
║ API: ✅ Online (42ms) ║
║ Sessions: 127 tracked ║
║ Events: 4,892 ingested ║
║ Hooks: 7/7 configured ║
║ Last Event: 3 minutes ago ║
╚══════════════════════════════════════╝
```Operate and maintain the local MCP server for this repository. Use for MCP tool updates, policy-guard changes, host configuration, and MCP runtime troubleshooting.
Run release-readiness checks for this repository. Use when validating docs, scripts, verification coverage, and operational safety before merge or release.
Understand this repository quickly before making changes. Use for architecture discovery, ownership mapping, command selection, and initial implementation planning.
Review backend route and hook logic for regressions, data integrity risks, and missing tests.
Review React UI changes for behavior regressions, state consistency, and UX breakage.
Review MCP server changes for tool safety, schema quality, and host integration correctness.
Debug production-like issues in this repository with disciplined evidence gathering. Use when fixing failing workflows, regressions, flaky behavior, or data inconsistencies across hooks, API, DB, websocket, and UI.
Operate and maintain the local MCP server for this project. Use when creating MCP host config, troubleshooting tool connectivity, modifying tool domains, or adjusting safety policy flags.