Identify stale and empty Claude Code sessions in the Agent Monitor and explain the cleanup endpoint (POST /api/settings/cleanup), always showing the exact list of what WOULD be removed before anything is deleted. Cleanup permanently deletes data, so this skill previews first and requires explicit user confirmation. Use when tidying the monitoring database.
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Find prune-worthy sessions and explain cleanup — preview first, delete only on explicit confirmation.
The user provides: $ARGUMENTS
preview → only show what would be removed (the safe default).confirm → the user has reviewed the preview and explicitly authorizes deletion.older than 7d) for what counts as stale.| Endpoint | Returns |
|---|---|
GET /api/sessions?limit=N | session list: id, status, model, cwd, started_at, ended_at, cost, metadata (turn_count, total_turn_duration_ms) |
GET /api/stats | totals: total_sessions, active_sessions, total_events, events_today, sessions_by_status, agents_by_status |
POST /api/settings/cleanup | runs the cleanup routine and returns what was removed — DESTRUCTIVE, only after confirmation |
GET /api/stats — record total_sessions, sessions_by_status, total_events. This is
the before-state to compare against.
GET /api/sessions?limit=1000. Flag sessions that are:
turn_count 0 / null and cost 0 (started but never
did anything).status active/working but last activity older than the
threshold (default 24h), i.e. never cleanly stopped.ended_at and no recent events.List every candidate with the reason it qualifies. State the total count and confirm that nothing has been deleted yet.
Describe POST /api/settings/cleanup: it prunes empty / orphaned sessions and their
dangling events server-side and returns a summary of removed rows. Make clear this
is permanent and not reversible from the dashboard.
If — and only if — $ARGUMENTS is confirm (or the user has explicitly approved
this run), call POST /api/settings/cleanup, then re-read /api/stats and report
the before → after delta. Otherwise stop after the preview and tell the user to
re-run with confirm.
A preview Markdown table: id (short) | status | reason | cwd basename | started_at | cost,
then a one-line count and the explicit "nothing deleted — re-run with confirm to
proceed" notice. On a confirmed run, add a before → after summary using ▲/▼ on the
counts. Currency as USD to 4 decimal places.
POST /api/settings/cleanup without an explicit confirm from the
user in this turn — previewing is the default.POST /api/settings/clear-data or any other destructive
endpoint; cleanup of stale/empty sessions only.npm start from
the repo root.还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Inspect fired CCAM alerts and manage alert rules for token thresholds, event patterns, inactivity, and status duration. Use when acknowledging alerts, creating or editing a rule, checking cooldowns, or connecting alert rules to webhook targets.
中文简介正在准备中。当前显示原文说明。
Identify anomalous sessions using Agent Monitor data — cost outliers from the pricing engine, token anomalies (cache miss spikes, compaction baseline surges), unusual event type ratios (PreToolUse/PostToolUse gaps, APIError clusters), behavioral deviations from workflow intelligence (complexity score outliers, error propagation anomalies), and sessions with abnormal metadata (extreme turn_count, high thinking_blocks, zero turn_duration).
中文简介正在准备中。当前显示原文说明。
Produce a detailed report on APIError events from Agent Monitor data — counts over time, which sessions and models are affected, and the likely root cause (rate limits, overload/529, or context-window pressure) inferred from each event's summary and data payload. Use when API errors spike or when you need to explain why requests are failing.
中文简介正在准备中。当前显示原文说明。
Benchmark one session (or a small recent set) against the rolling average using Agent Monitor data — cost, total tokens, tool count, and workflow complexity score — and report where each metric lands as a percentile of the population. Tells you whether a session was normal, cheap, or an outlier. Use when judging whether a session was typical or out of band.
中文简介正在准备中。当前显示原文说明。
Define a spend budget for Claude Code and, optionally, create a cost alert rule that fires when usage crosses the limit, via POST /api/alerts/rules on the Agent Monitor dashboard. Reads current spend from /api/pricing/cost to size the budget sensibly and explains every rule field before writing. Use when setting a spend limit or wiring up a budget guardrail.
中文简介正在准备中。当前显示原文说明。
Analyze prompt-cache effectiveness for Claude Code usage from the Agent Monitor dashboard — cache hit rate (total_cache_read / (total_cache_read + total_input)), cache_write vs cache_read reuse, cache-read vs cache-write spend, and the sessions with the poorest reuse. Pulls token totals from /api/analytics, per-session detail from /api/sessions, and dollar splits from /api/pricing/cost. Use when diagnosing cache spend or deciding whether prompt caching is paying off.
中文简介正在准备中。当前显示原文说明。