Weekly Digests

Most timeline tools give you one giant report. This one gives you a serial narrative, one chapter per ISO week, where each subagent reads what the previous week wrote and continues the story. It's for when you want to see how a project evolved week by week, not just what happened overall. The carry-forward discipline is strict: each agent gets 350 words to brief the next one, so dead threads get pruned and only live arcs survive. Works best on projects with real duration. A three day prototype gets you three chapters and that's fine, but a six month build gets you the kind of serialized dev diary you'd actually want to reread. The tone instructions are opinionated but you can edit the prompt template.

install copies · 90 days. Times the install command was copied on this site in the last 90 days, bots filtered.: 7
skills.sh installs: 4.3K
GitHub stars: 115.5K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add thedotmack/claude-mem --skill weekly-digests --agent claude-code

Installs into .claude/skills of the current project.

Files

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 $WORKER_PORT):

SKILL.md on GitHub