debug-live-issue
Debug production-like issues in this repository with disciplined evidence gathering. Use when fixing failing workflows, regressions, flaky behavior, or data…
Polls the Agent Monitor /api/stats endpoint several times over a short window and reports the live deltas in active_sessions, active_agents, events_today, and ws_connections so you can see activity moving in real time. Use when watching the dashboard for live changes rather than
$ npx -y skills add hoangsonww/Claude-Code-Agent-Monitor --skill live-watch --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/live-watchContext preview
The summary Claude sees to decide when to auto-load this skill.
Polls the Agent Monitor /api/stats endpoint several times over a short window and reports the live deltas in active_sessions, active_agents, events_today, and ws_connections so you can see activity moving in real time. Use when watching the dashboard for live changes rather than
name: live-watch description: > Polls the Agent Monitor /api/stats endpoint several times over a short window and reports the live deltas in active_sessions, active_agents, events_today, and ws_connections so you can see activity moving in real time. Use when watching the dashboard for live changes rather than a one-time snapshot.
Watch the dashboard's live counters change over a short window by polling `/api/stats` a few times and reporting the deltas.
The user provides: **$ARGUMENTS**
Interpreted as the watch shape: number of polls and/or interval (e.g. `5x3s` = 5 samples 3 seconds apart). Defaults when empty: **5 samples, ~3 seconds apart** (a ~15-second window). A bare number means that many samples at the default interval; a bare duration means the default sample count at that interval.
| Endpoint | Returns | |----------|---------| | `GET /api/stats` (polled) | `{ total_sessions, active_sessions, active_agents, total_agents, total_events, events_today, ws_connections, agents_by_status, sessions_by_status }` |
Poll `GET /api/stats` once per interval for the configured number of samples, recording the timestamp and the four watched counters each time. Pace the polls with a short wait between requests; keep the total window short (seconds, not minutes) so it stays interactive.
If the very first poll fails to connect, the dashboard is down — stop and tell the user to start it with `npm start` (or `npm run dev`) from the repo root, then retry.
State the sample count, interval, and total elapsed window.
A Markdown table — one row per poll — with columns: `#`, `time`, `active_sessions`, `active_agents`, `events_today`, `ws_connections`.
For each of the four watched counters, report the net change from the first to the last sample using ▲ (increase), ▼ (decrease), or `=` (no change). Note any mid-window spikes or dips visible in the timeline.
One line: is the dashboard actively receiving traffic (counters moving) or idle (flat) over the window?
🚀 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…