How do I install the Logbook:time skill?

Run npx skillmds@latest add florianbuetow/logbook-time in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Logbook:time safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Logbook:time?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Logbook:time free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Logbook:time?

florianbuetow (@florianbuetow) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Logbook:time by florianbuetow — Agent Skill

Name: Logbook:time
Author: florianbuetow

Logbook:time

Analyze time spent per project across all Claude Code sessions. Generates monthly and yearly markdown reports with per-project/branch breakdowns. Use when the user asks about "time spent", "hours per project", "session time", "time report", "logbook time", or wants to know how long they spent coding.

File contents

Logbook — Time Report

Generate time-per-project reports from Claude Code session logs. Groups branches under their parent project. Excludes idle gaps > 15 minutes.

Workflow

Step 1: Run the analysis script

The script lives at the plugin path. Find it relative to this skill:

SCRIPT="$(dirname "$(dirname "$(dirname "$0")")")/scripts/logbook.py"

But in practice, run it from the project root:

python3 plugins/logbook/scripts/logbook.py time --out docs/reports

This generates:

One file per calendar month: YYYYMM-logbook-time.md
One file per year: YYYY-logbook-time.md

To limit to a specific period:

python3 plugins/logbook/scripts/logbook.py time --year 2026 --month 3 --out docs/reports

For preview only (no files written):

python3 plugins/logbook/scripts/logbook.py time --preview

Step 2: Show the 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.

Step 3: List generated files

Show the user which report files were created and their paths.

Report Structure

Each report contains:

Summary — total active time, project count, session count
Top 10 table — project name + time
Detailed breakdown — every project with branch-level rows showing time and session counts

Notes

Gaps > 15 minutes between messages are excluded (configurable in script as GAP_THRESHOLD)
Branches are detected from git worktree patterns (-git-<branch>, --claude-worktrees-<branch>)
Excluded projects are configured in the EXCLUDED list in the script

---name: logbook-timedescription: Analyze time spent per project across all Claude Code sessions. Generates monthly and yearly markdown reports with per-project/branch breakdowns. Use when the user asks about "time spent", "hours per project", "session time", "time report", "logbook time", or wants to know how long they spent coding.---# Logbook — Time ReportGenerate time-per-project reports from Claude Code session logs. Groups branches under their parent project. Excludes idle gaps > 15 minutes.## Workflow### Step 1: Run the analysis scriptThe script lives at the plugin path. Find it relative to this skill:```bashSCRIPT="$(dirname "$(dirname "$(dirname "$0")")")/scripts/logbook.py"```But in practice, run it from the project root:```bashpython3 plugins/logbook/scripts/logbook.py time --out docs/reports```This generates:- One file per calendar month: `YYYYMM-logbook-time.md`- One file per year: `YYYY-logbook-time.md`To limit to a specific period:```bashpython3 plugins/logbook/scripts/logbook.py time --year 2026 --month 3 --out docs/reports```For preview only (no files written):```bashpython3 plugins/logbook/scripts/logbook.py time --preview```### Step 2: Show the previewAfter 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.### Step 3: List generated filesShow the user which report files were created and their paths.## Report StructureEach report contains:1. **Summary** — total active time, project count, session count2. **Top 10 table** — project name + time3. **Detailed breakdown** — every project with branch-level rows showing time and session counts## Notes- Gaps > 15 minutes between messages are excluded (configurable in script as `GAP_THRESHOLD`)- Branches are detected from git worktree patterns (`-git-<branch>`, `--claude-worktrees-<branch>`)- Excluded projects are configured in the `EXCLUDED` list in the script

Frequently asked questions