claude-usage-analyst
Analyze Claude Code and Claude Desktop Code token usage, cost, quota burn, model mix, cache read/write, and 5-hour block consumption using ccusage evidence. Use when the user asks why Claude quota was exhausted, whether a model such as fable/opus/sonnet is unusually expensive, how many tokens were spent today or historically, or needs a human-friendly explanation of local Claude Code CLI/Desktop usage.
pinned to #029876dupdated last month
Ask your AI client: “install skills/claude-usage-analyst”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/claude-usage-analystmetahub onboarded this repo on the author's behalf.
If you own github.com/daymade/claude-code-skills on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
1,331
Last commit
last month
Latest release
published
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.029876d· last month
Behavioral checks ran but aren't published for this artifact; the static checks above ran at publish time.
Documentation
6 passed3 warningsTags / topics declaredwarn
No manifest tags and no GitHub repo topics
Add tags to the manifest (or GitHub topics on the repo) so the registry's search and category filters surface this artifact.
Homepage or repository declaredwarn
No homepage or repository declared.
Add a "homepage" or "repository" field to SKILL.md.
Documentation shows usagewarn
Documentation has no code examples.
Add at least one fenced example showing a real invocation.
Description quality
61 words · 405 chars — "Analyze Claude Code and Claude Desktop Code token usage, cost, quota burn, model…"
README is present and substantial
182,381 chars · 15 sections · 88 code blocks
README has usage / example sections
found: Example
Homepage / docs URL declared
no homepage declared (registry will use the repo URL) — info-only, not blocking
Description is substantive
Description is 61 words.
Documentation present and substantive
Documentation present (SKILL.md, 399 words).
Release history
1- releasecurrent029876dwarnlast month
Contents
Overview
Use this skill to produce evidence-based usage explanations from local ccusage data. Separate observed numbers from interpretation, and explain quota burn in human terms.
Workflow
-
Verify
ccusageis available:ccusage --versionIf missing, install or update with
npm install -g ccusage@latestor run withnpx ccusage@latest. -
Run the bundled analyzer for the requested window:
python3 /path/to/claude-usage-analyst/scripts/analyze_claude_usage.py \ --since YYYY-MM-DD --until YYYY-MM-DD --timezone Asia/ShanghaiDefault
--since/--untilis today in the selected timezone. For historical comparison, set--sinceto an earlier date such as the first day of the month; otherwise rank/median fields only describe the single target day. -
If the user asks about a specific model comparison, pass aliases:
python3 scripts/analyze_claude_usage.py --model-a fable --model-b opus-4-8 -
Read
references/explanation-guide.mdwhen writing the final answer.
Evidence Rules
- Base numeric claims on
ccusageoutput or the bundled analyzer output. - State the scope:
ccusage claudemeasures local Claude Code usage logs, including Claude Desktop's Claude Code sessions when those local logs exist. It is not a complete ordinary Claude.ai chat bill. - Report dates with timezone.
- Explain cache clearly: cache read tokens are still usage/quota pressure even though the user did not type those words.
- Do not infer Anthropic plan quota rules from local token counts unless the user provides plan details. Say "quota-like pressure" or "ccusage estimated cost/token burn" when exact plan accounting is unknown.
- When comparing models, compare both token volume and estimated cost. A model can have similar token volume but higher cost.
Output Shape
Use this structure unless the user asks otherwise:
- Short conclusion in plain language.
- Evidence table: total tokens, cost, input, output, cache create, cache read.
- Model comparison table.
- 5-hour block table when quota exhaustion is discussed.
- Explanation of why the burn happened.
- Confidence and caveats.
Keep the answer readable for non-technical users. Avoid unexplained terms like "cache read" without a one-sentence translation.
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/claude-usage-analyst