receipts
Generate a personal Claude Code usage & impact report ("receipts") from this machine's local session transcripts — for justifying Claude Code usage/spend to a manager, self-review, or "what have I been using this for" check-ins. Mines ~/.claude/projects locally (no extra API calls beyond one final write-up), cross-references local git history, and writes a markdown report plus a self-contained HTML receipt to your home directory. Use when the user asks for "receipts", an "impact report", "usage report", wants to "show my Claude Code activity", "prove the value of Claude Code", or runs `/receip
Profile →npx skills add anthropics/claude-plugins-official --skill receipts --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# /receipts — personal Claude Code impact report Generates a markdown report of one developer's own Claude Code activity, built entirely from local data: - **Source data**: this machine's session transcripts at `~/.claude/projects/**/*.jsonl` (every session, every project, already on disk — nothing to set up). - **Cost**: the mining step is a local Node script — file I/O + regex, zero API calls. The only model call is one final write-up over a small (~10-20KB) JSON summary, regardless of how much history was scanned. - **Cross-reference**: local `git log` per repo (no network) to sanity-check commit activity against CC session activity. ## Step 1 — figure out the period Parse `$ARGUMENTS`: - "week" → 7, "month" → 30 (default if nothing given), "quarter" → 90, "year" → 365 - a bare number → that many days - a project name/substring (e.g. "for anthropic") → pass through as `--repo <substr>`. It matches against the resolved project name, case-insensitively, and scopes the entire report — totals included — to matching projects. ## Step 2 — run the miner The script `mine-transcripts.mjs` ships alongside this SKILL.md, under `scripts/`. Use its absolute path: ```bash node <skill-dir>/scr
- Step 1 — figure out the period
- Step 2 — run the miner
- What the numbers mean
- Step 3 — write the report (one model call, from the JSON only)
- Header
- What you shipped
- By project
- Don't add a "where the spend went" section
- Framing for a manager
- Step 4 — save the markdown
- Step 5 — save the HTML receipt locally
- Step 6 — wrap up
node <skill-dir>/scripts/mine-transcripts.mjs --days <N> [--repo <substr>] --html /tmp/cc-receipt.html
What does the receipts skill do?
Generate a personal Claude Code usage & impact report ("receipts") from this machine's local session transcripts — for justifying Claude Code usage/spend to a manager, self-review, or "what have I been using this for" check-ins. Mines ~/.claude/projects locally (no extra API calls beyond one final write-up), cross-references local git history, and writes a markdown report plus a self-contained HTML receipt to your home directory. Use when the user asks for "receipts", an "impact report", "usage report", wants to "show my Claude Code activity", "prove the value of Claude Code", or runs `/receip
How do I install it?
Run `npx skills add anthropics/claude-plugins-official --skill receipts --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From anthropics/claude-plugins-official, a repository with 33,027 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.