Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From logbook
Generates monthly and yearly markdown reports analyzing message counts per project/branch from Claude Code session logs, separating human-typed from automated messages. Activates for usage statistics queries.
How this skill is triggered — by the user, by Claude, or both
Slash command
/logbook:messagesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate message-count reports from Claude Code session logs. Groups branches under their parent project. Separates human-typed messages from automated user turns (tool results, hooks).
Generate message-count reports from Claude Code session logs. Groups branches under their parent project. Separates human-typed messages from automated user turns (tool results, hooks).
python3 plugins/logbook/scripts/logbook.py messages --out docs/reports
This generates:
YYYYMM-logbook-messages.mdYYYY-logbook-messages.mdTo limit to a specific period:
python3 plugins/logbook/scripts/logbook.py messages --year 2026 --month 3 --out docs/reports
For preview only (no files written):
python3 plugins/logbook/scripts/logbook.py messages --preview
After running the script, display the top 10 table from stdout directly to the user. This is the inline preview — do NOT hide it behind a file path.
Show the user which report files were created and their paths.
Each report contains:
The reports show "You" (human-typed) and "Agent" counts for clarity.
npx claudepluginhub florianbuetow/claude-code --plugin logbookGenerates a personal Claude Code usage & impact report from local session transcripts and git history. Useful for justifying spend, self-review, or activity check-ins.
Analyzes Claude Code session logs to improve prompt quality, optimize tool usage, track costs, and identify productivity patterns including peak hours and common errors.
Generates standup summaries of recent Claude Code sessions: lists done commits by project/branch/duration, in-progress tasks, and metrics like total time/sessions.