Insights
Answer questions about the user's own Claude Code usage history — sessions, hours, streaks, error rate, burnout risk, cost/cache savings, most-used tools, and git commit activity — using the locally installed cc-atlas CLI. Use whenever the user asks about their Claude Code usage, productivity, burnout, streaks, cost, or activity history. Entirely local, no network calls.From its SKILL.md
npx -y skills add sasly2048/cc-atlas --skill insightsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.2 KB, as published. Nobody here has run it
cc-atlas usage insights
cc-atlas is a bundled CLI that reads the user's local ~/.claude/projects
session transcripts (and any git repos they've configured) into a local
SQLite database and computes usage analytics. Nothing leaves the machine —
no API calls, no telemetry.
Workflow
- Run
cc-atlas syncfirst. It's safe and fast to re-run — incremental, only re-parsing transcript files that changed since the last sync. - For a specific question, prefer
cc-atlas ask "<question>". It understands a fixed vocabulary — hours, sessions, error rate, streak, burnout, most-used tool, cost, commits — optionally scoped to a project name and a period (today / this week / this month / all time). It is pattern-matching, not a language model. If it replies "I didn't recognize that one," fall back tocc-atlas export --format jsonand compute the answer yourself from the returned summary rather than guessing. - For a one-line snapshot (streak, hours today, burnout risk), use
cc-atlas status --json. - For a fuller written report, use
cc-atlas report <day|week|month> --format markdown.
What this can't answer directly
Cross-project comparison, session replay, team activity, anomaly
detection, and goal tracking are interactive-only menu screens — they need
a real terminal to select options. If the user wants one of those, tell
them to run cc-atlas directly in their own terminal to open the menu.
Don't try to drive interactive prompts through a tool call.
Be honest about the numbers
- Dollar figures use an illustrative blended rate, not Anthropic's actual per-model pricing — say so if you report a cost.
- If
cc-atlas syncfinds no session data yet, say that plainly rather than presenting a zero as a real answer.