/mission-log — session activity harvest

~/.claude/projects/

🤖 R2-D2 moment: an astromech's flight recorder never sleeps — after the X-wing lands, the mechanic pulls out the log. The record is always there; what you need is a reader.

Usage

/mission-log [date]

yesterday

YYYY-MM-DD

Actions

1. Run the harvester (script bundled with this skill, pure standard library, zero tokens):
   bash

   python3 <this skill directory>/scripts/harvest.py --date <date>

   For each active session it outputs: time range, project@branch, turns, token usage, model, tool histogram, user's verbatim messages (first 5). Add

   --format jsonl

   for machine-readable output.
2. Present: show the skeleton to the user; if the user asks for details about a session, deep-read that transcript as needed (the skeleton has the session id prefix to locate it), and warn before deep-reading that it will consume more context.

Rules

• 🚫 Read-only: this skill writes no files and changes no state; writing files is /daily-debrief's job.
• ✅ The skeleton is the source of truth: do not invent activity that isn't in the skeleton; if no data is found, report "no record for that day".
• ⚠️ Lookback limit = transcript retention period: Claude Code deletes transcripts after 30 days by default (

  cleanupPeriodDays

  can be increased); dates beyond the retention period have nothing to harvest — say so directly.

Advanced: cross-machine harvesting

ssh <your host> "python3 - --date <date>" < <this skill directory>/scripts/harvest.py