Time Blame — Productivity skill for Claude Code
Claude Code mod: after each turn, says whether the time went to Claude, your tools or you.
How to install Time Blame
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open karanb192/time-blame and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Time Blame does
Claude Code mod: after each turn, says whether the time went to Claude, your tools or you.
Alternatives in Productivity
- Configure Claude HUD — FIRST: Use the Read tool to load ~/.claude/plugins/claude-hud/config.json if it exists 10.9k ★
- Close The Quarter — Workflow recipe — turn the quarter's raw numbers into a leadership story and board deck by chaining 4 skills 1.3k ★
- Chief — CLI that wraps Claude Code in a loop 396 ★
README
time-blame
A Claude Code mod that answers one question after every turn: was Claude slow, or was it your `npm test`?
It splits each turn's time by cause and shows it under the answer: in the terminal as a coloured line in place of Claude Code's "Worked for" line, elsewhere as a dim log line. `/blame` opens a panel with the whole session's split as a coloured bar. Claude never reads any of it, and nothing leaves your machine.

A real run on Claude Code 2.1.302, in a small demo project whose test suite takes about 13 seconds. The waits are shown at 6× speed, as the clip says. Of the 47 seconds, Claude took 15 and `npm test` took 27. [Watch it as a video](https://timeblame.aidojo.si/#watch).
The same two outputs in plain text, from an earlier live session. This is what you get outside the terminal, or where nothing can draw a panel:
⏺ time-blame: 26s · Claude 8.0s (7.2s before output) · sleep 4.7s · you 12s · other 0.3s
⏺ time-blame: this session, this machine · 1 turn · 26s of turn time
⏺ time-blame: Claude 8.0s 31% before output 7.2s, writing 0.8s
⏺ time-blame: tools 4.7s 19% sleep 4.7s
⏺ time-blame: you 12s 49% approvals 12s
⏺ time-blame: other 0.3s 1% not attributed: hooks, local work, gaps
⏺ time-blame: longest turn 26s. Times are summed waits measured in this session, not server speed.
Both blocks are copied as text from that session, where a permission dialog was left open for 12 seconds before it was approved.
Install
claude plugin marketplace add karanb192/time-blame
claude plugin install time-blame@time-blame
Then restart Claude Code or run `/reload-plugins`. Mods are on by default from Claude Code 2.1.287; time-blame needs 2.1.302 or later. To try it for one session without installing, clone the repo and run `claude --
Related Skills
Chronos
Show where this session's time actually went - active time, per-tool breakdown, repeated calls, slowest calls,
Time Block
Plan the week's focus and admin blocks around your meetings and book them in your own Outlook calendar as appo
MarkovModel
Markov Text Generation Problem Description The Infinite Monkey Theorem1 (IFT) says that if a monkey hits keys
Jobbox
Every command your agent runs is wrapped; the slow ones put themselves in the BACKGROUND and tell you when the
Subagent Monitor
A Claude Code mod that shows your subagents in a sidebar, each with an animated pixel crab. See what every age
Gov Metrics
Governance metrics — measure whether the gates actually work. Block rate, override/waiver rate, false-block pr
Related Agents
Retro
Retrospective facilitator that captures learnings from sprints and sessions, surfaces past insights, and compo
Copy Source Checker
Resolves every source a copy draft cites (PMID, DOI, URL, named study, regulation) and reports whether the sou
History Reviewer
Git history-aware reviewer. Use when changes touch code with non-trivial history, or to check whether a fix ac