Agent skill · writing content · thedotmack
weekly-digests
Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests", "week-by-week story", "serial timeline", or "narrative chapters" of a project's history.
Why this skill is useful
Adds a Python script that automates the generation of weekly narrative digests from project timelines, which the AI wouldn't reliably generate on its own.
What it needs
Requires curl, python installed locally. About 8k tokens when loaded. Last updated 2026-08-05. 89,894 stars on the source repository.
What this skill does
Weekly Digests Produce a serial, multi-chapter narrative digest of a project's complete claude-mem history. Differs from timeline-report (one long report) — this generates one digest per ISO week, with each subagent reading the prior week's carry-forward block so the story stays coherent. The chapter count equals the number of ISO weeks the timeline covers. A project with 2 weeks of data produces 2 chapters; one with 30 weeks produces 30. There is no fixed length — count the weeks first, then drive the pipeline off that count. When to Use Trigger when the user asks for: "Weekly digests" "Week-by-week story" "Serial timeline" "Story chapters of [project]" "Run a digest for each week" "Continue the story week by week" If the user wants a single sweeping report, use timeline-report instead. This skill is for serial chapter format. Prerequisites claude-mem worker running Project has at least one ISO week of observations (the pipeline degenerates gracefully — even N=1 works) A clean output directory the user is comfortable writing into Resolve the worker port (do this once, reuse $WORKERPORT): Workflow Step 1: Determine the Project Name Same worktree-detection pattern as timeline-report. In a worktree, the data source is the parent project: Step 2: Fetch the Full Timeline and Save It Sanity-check: confirm the file is non-empty and has the expected structure (preamble, then date headers like ### Mon DD, YYYY, then numeric observation lines <id> <time> <emoji> <title> and session boundary lines S<n> <prompt> (Mon DD at HH:MMpm)). Step 3: Split the Timeline Into Per-ISO-Week Files Write a Python script to .scratch/split-timeline.py that: 1. Parses date headers (### Mon DD, YYYY). 2. Groups days into ISO weeks via date.isocalendar() (Monday-start). 3. Emits one file per week to docs/timeline-weeks/<YYYY>-W<NN>-<MonDD>-to-<MonDD>.md, preserving each day's section verbatim. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills thedotmack/weekly-digests