跳到正文
cccskills
免费在 GitHub 公开

session-compare

Compare two sessions side-by-side using Agent Monitor data — per-model token usage (input/output/cache_read/cache_write + compaction baselines), pricing engine cost breakdowns, workflow intelligence (complexity scores, tool flow transitions, subagent effectiveness), session metadata (thinking_blocks, turn_count, turn_duration_ms, usage_extras), and full event timelines with all 10+ event types.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(2)

  • SKILL.md3.1 KB
  • agents/openai.yaml273 B

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Session Compare

Compare two Claude Code sessions side-by-side using Agent Monitor data.

Input

The user provides: $ARGUMENTS

This may be:

  • Two session IDs: "abc123 def456"
  • "best vs worst" — compare highest and lowest productivity sessions
  • "latest 2" — compare the two most recent sessions
  • A session ID + "vs average" — compare one session against the baseline

Procedure

  1. Identify sessions to compare:

    • If two IDs given: fetch both from http://localhost:4820/api/sessions/{id}
    • If "best vs worst": fetch sessions, score by completion + cost efficiency, pick extremes
    • If "latest 2": GET /api/sessions?limit=2 (default sort: most recently updated first)
    • If "vs average": fetch session + compute averages from last 50 sessions
  2. Gather detailed data for each session:

    • Session metadata: GET /api/sessions/{id}
    • Events: GET /api/events?session_id={id}
    • Agents: GET /api/agents?session_id={id}
    • Cost: GET /api/pricing/cost/{id}
  3. Build comparison:

    Overview Comparison

    MetricSession ASession BDifference
    Statuscompletederror—
    Modelsonnet-4sonnet-4same
    Duration12m 34s45m 12s+32m 38s
    Total Cost$0.0234$0.1456+522%
    Events45187+315%
    Tools Used812+4
    Error Count07+7
    Agents25+3

    Token Comparison

    Token TypeSession ASession BDifference
    InputNN±N%
    OutputNN±N%
    Cache ReadNN±N%
    Cache WriteNN±N%
    EfficiencyN%N%±N%

    Tool Usage Comparison

    • Tools unique to Session A
    • Tools unique to Session B
    • Shared tools with usage count comparison
    • Error rate per tool in each session

    Timeline Comparison

    • Side-by-side event timeline
    • Where sessions diverged in approach
    • Key decision points that led to different outcomes

    Agent Activity Comparison

    • Agent counts and types
    • Subagent strategy differences
    • Agent success rates
  4. Analysis:

    • Why one session was more efficient/successful than the other
    • Key decisions that made the difference
    • Lessons to apply to future sessions

Output Format

Present as a side-by-side comparison report with:

  • Executive comparison summary (which session was "better" and why)
  • Structured comparison tables with color-coded differences (green = better, red = worse)
  • A "Lessons Learned" section with actionable takeaways
  • Overall winner declaration with justification

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

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.

中文简介正在准备中。当前显示原文说明。

hoangsonww/Claude-Code-Agent-Monitor11082026年10月23日 更新

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).

中文简介正在准备中。当前显示原文说明。

hoangsonww/Claude-Code-Agent-Monitor11082026年10月23日 更新

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.

中文简介正在准备中。当前显示原文说明。

hoangsonww/Claude-Code-Agent-Monitor11082026年10月23日 更新

benchmark

免费

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.

中文简介正在准备中。当前显示原文说明。

hoangsonww/Claude-Code-Agent-Monitor11082026年10月23日 更新

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.

中文简介正在准备中。当前显示原文说明。

hoangsonww/Claude-Code-Agent-Monitor11082026年10月23日 更新

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.

中文简介正在准备中。当前显示原文说明。

hoangsonww/Claude-Code-Agent-Monitor11082026年10月23日 更新

查看 hoangsonww 的全部技能

报告此技能的问题