debug-live-issue
Debug production-like issues in this repository with disciplined evidence gathering. Use when fixing failing workflows, regressions, flaky behavior, or data…
Quick dashboard health and status overview — checks the Agent Monitor API (port 4820), reports session/agent/event counts from /api/stats, confirms WebSocket connectivity, reads the redacted hook status returned by /api/settings/info, and shows data freshness (last event
$ npx -y skills add hoangsonww/Claude-Code-Agent-Monitor --skill dashboard-status --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/dashboard-statusContext preview
The summary Claude sees to decide when to auto-load this skill.
Quick dashboard health and status overview — checks the Agent Monitor API (port 4820), reports session/agent/event counts from /api/stats, confirms WebSocket connectivity, reads the redacted hook status returned by /api/settings/info, and shows data freshness (last event
name: dashboard-status description: > Quick dashboard health and status overview — checks the Agent Monitor API (port 4820), reports session/agent/event counts from /api/stats, confirms WebSocket connectivity, reads the redacted hook status returned by /api/settings/info, and shows data freshness (last event timestamp). Use to verify the monitoring system is operational.
Quick status check on the Claude Code Agent Monitor dashboard.
The user provides: **$ARGUMENTS**
Options: empty (default: full status), "quick" (API only), "verbose" (include endpoint details).
| 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) |
From `/api/stats`:
From latest event:
Use `/api/settings/info` → `hooks` for configured hook names:
unrelated settings.
From `/api/settings/info`:
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 ║ ╚══════════════════════════════════════╝
🚀 A real-time monitoring dashboard for Claude Code & Codex, built with SQLite3, Node.js, Express, React, Vite, TailwindCSS, & WebSockets. It tracks sessions, agent activity, tool usage, and subagent orchestration, providing live analytics, a Kanban status board, status notifications, a cute buddy, & an interactive web UI/MacOS/Windows native app.
Repo: hoangsonww/Claude-Code-Agent-Monitor
Debug production-like issues in this repository with disciplined evidence gathering. Use when fixing failing workflows, regressions, flaky behavior, or data…
MANDATORY for every coding agent (Claude Code, Codex, or any other) on every change-set — every applicable source file the agent creates or updates MUST start…
MANDATORY for every coding agent and contributor touching localized content — keep all five localization surfaces (dashboard UI keys, wiki page, mirrored…
Operate and maintain the local MCP server for this project. Use when creating MCP host config, troubleshooting tool connectivity, modifying tool domains, or…
Push the current working tree directly to a GitHub PR whose head lives on a **fork**, without creating a new branch and without pushing to `origin` (which is…
Onboard quickly to this repository. Use when asked to understand architecture, locate ownership, choose the right module, or identify the correct commands and…