ClaudeSuperPower
SubmitLog in

receipts

Skill

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 w

32.8KFrontend

Install

git clone https://github.com/anthropics/claude-plugins-public.git ~/.claude/skills/receipts

What is 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 `/receipts`.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~151 tokens of context used while enabled, before you invoke anything

Trust

94/100 · Excellent

1 factor scored below maximum

Documentation

README · ~12 min read

/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.

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.

Subagents

All subagents →

code-architect

Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create/modify, component designs, data flows, and build sequences

32.8K stars

plugin-validator

Use this agent when the user asks to "validate my plugin", "check plugin structure", "verify plugin is correct", "validate plugin.json", "check plugin files", or mentions plugin validation. Also trigger proactively after user creates or modifies plugin components. Examples: <example> Context: User f

32.8K stars

scan-inventory

Restricted read-only repository cartographer dispatched by the Claude Security scan workflow to partition the tree into components and account for every top-level directory; not for direct invocation or vulnerability research.

32.8K stars