What problem does it solve?
Query Claude Code's JSONL session logs via DuckDB for usage analytics, tool patterns, error forensics, and routing decisions. Use when the user asks about their Claude usage patterns, tool frequencies, error rates, permission denials, agent routing, skill invocations, MCP server usage, session timelines, or any question about "how has Claude been working". This skill turns ~900MB of raw JSONL into a queryable DuckDB database — use it instead of writing ad-hoc Python scripts to parse logs. Do NOT use for debugging current code issues, reading individual session transcripts, or questions about Claude's capabilities — this skill is for aggregate usage analytics across historical sessions.
Core Features & Use Cases
- Ingest and consolidate historical JSONL logs into a unified analytics store.
- Analyze tool usage patterns, error frequencies, and session timelines across sessions.
- Respond to questions about long-term usage trends and routing decisions using SQL-backed insights.
Quick Start
Run ingestion with python3 scripts/ingest.py to ingest logs, then query the DuckDB database for analytics.