Analytics

Queries local OrchestKit analytics across agents, skills, hooks, teams, and sessions with privacy-safe hashed project IDs. Nine subcommands cover everything from model delegation breakdowns to session replays and cost estimation with cache savings. All data lives in `~/.claude/analytics/` as JSONL files you can query with jq. The otel subcommand surfaces CC 2.1.117+ telemetry like slash command frequency and effort-vs-success correlation. Graceful fallbacks handle missing data and rotated files. If you're running multi-agent workflows or tracking token costs across projects, this gives you a local dashboard without sending anything off-box. Built for teams who want visibility without vendor lock-in.

skills.sh installs: 210
GitHub stars: 301
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add yonatangross/orchestkit --skill analytics --agent claude-code

Installs into .claude/skills of the current project.

Files

Cross-Project Analytics

Query local analytics data from ~/.claude/analytics/. All data is local-only, privacy-safe (hashed project IDs, no PII).

Answer usage questions from the local files, never from guesswork: agent usage (which agents and how often — not which model, see the caveats) lives in ~/.claude/analytics/agent-usage.jsonl; hook performance and failures live in ~/.claude/analytics/hook-timing.jsonl; token and cost totals live in ~/.claude/stats-cache.json. Query them with jq one-liners (below) and present real counts, not pointers to dashboards.