본문으로 건너뛰기
cccskills
무료GitHub에 공개

usage-trends

Analyze Claude Code usage trends over time using the Agent Monitor's analytics API — daily session counts, daily event counts, token volumes by type, model distribution, tool usage rankings, and agent/event type distributions across 365-day retention windows.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(2)

  • SKILL.md3.3 KB
  • agents/openai.yaml263 B

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Usage Trends

Analyze usage patterns and trends from the Agent Monitor analytics data.

Input

The user provides: $ARGUMENTS

Options: "last 7 days", "last 30 days", "last quarter", "peak hours", "tool trends", "model usage".

Data Sources

EndpointReturns
GET /api/analyticsComprehensive analytics object (see schema below)
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/sessions?limit=200Full session records with timestamps and metadata

Analytics response schema (GET /api/analytics)

{
  "overview": { "total_sessions", "active_sessions", "active_agents", "total_agents", "total_events" },
  "tokens": {
    "total_input": N, "total_output": N,
    "total_cache_read": N, "total_cache_write": N
  },
  "tool_usage": [{ "tool_name": "...", "count": N }],  // top 20
  "daily_events": [{ "date": "YYYY-MM-DD", "count": N }],  // 365 days
  "daily_sessions": [{ "date": "YYYY-MM-DD", "count": N }],  // 365 days
  "agent_types": [{ "subagent_type": "task"|"explore"|null, "count": N }],
  "event_types": [{ "event_type": "PreToolUse"|"PostToolUse"|..., "count": N }],
  "avg_events_per_session": N,
  "total_subagents": N,
  "sessions_by_status": { "active": N, "completed": N, "error": N, "abandoned": N },
  "agents_by_status": { "working": N, "completed": N, "error": N, ... }
}

Trend Analyses to Produce

1. Daily Activity Trend

Plot daily_sessions and daily_events for the requested period. Compute:

  • Average sessions/day and events/day
  • Week-over-week delta (%)
  • Peak day and quietest day

2. Token Volume Trends

From analytics tokens (baselines are pre-summed into totals at the DB level):

  • Total tokens: total_input, total_output, total_cache_read, total_cache_write
  • Cache efficiency over time: total_cache_read / (total_cache_read + total_input) — trending up = improving
  • Output intensity: total_output / total_input ratio — high = Claude is verbose

3. Tool Usage Ranking

From tool_usage (top 20 tools by event count):

  • Bar chart data (tool name → count)
  • Tool diversity: unique tools used
  • Subagent spawns: count of "Agent" tool uses (each = a subagent launched)

4. Model Distribution

From agent_types + per-session model field:

  • Which models are used most frequently
  • Subagent type distribution: main (null) vs task vs explore vs code-review

5. Session Health Distribution

From sessions_by_status:

  • Completion rate: completed / total × 100
  • Error rate: error / total × 100
  • Abandoned rate: abandoned / total × 100

6. Event Type Distribution

From event_types:

  • PreToolUse/PostToolUse ratio (should be ~1:1; gap = tools failing)
  • Compaction frequency relative to session count
  • APIError count (quota hits, rate limits, overloaded)

Output

Markdown with tables and ASCII trend indicators (▲▼→). Include period comparison when applicable.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 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-Monitor1.1천2026년 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-Monitor1.1천2026년 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-Monitor1.1천2026년 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-Monitor1.1천2026년 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-Monitor1.1천2026년 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-Monitor1.1천2026년 10월 23일 업데이트

hoangsonww의 스킬 모두 보기

이 스킬의 문제 신고