Skip to content
Development
Skill

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

From plugin
claude-code-agent-monitor
1k75 skills21 agents33 commands1 MCP
Install
$ npx -y skills add hoangsonww/Claude-Code-Agent-Monitor --skill usage-trends --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/usage-trends

Context preview

The summary Claude sees to decide when to auto-load this skill.

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.

SKILL.md

usage-trends.SKILL.md
name: usage-trends
description: >
  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.

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

| Endpoint | Returns | |----------|---------| | `GET /api/analytics` | Comprehensive 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=200` | Full 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.

Read more
Ships withclaude-code-agent-monitor

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

Get the whole plugin

Other skills on claude-code-agent-monitor.