Weekly Digests
Splits a project's full claude-mem timeline into ISO weeks and writes one serialized narrative chapter per week, each inheriting the previous week's carry-forward.
What it does
This skill pulls a project's complete timeline from the claude-mem worker, splits it into per-ISO-week files (Monday start), and produces exactly as many chapters as there are weeks with data. The key mechanic is a strictly sequential subagent pipeline: each week's agent receives the prior week's carry-forward block (~350 words covering active arcs, the "cast" of recurring systems, unresolved threads, and tone notes), so you get one continuous serial story instead of N disconnected summaries.
- Generates raw per-week source files plus a README index table (week, dates, observations, sessions)
- Narrative budget scales with volume (<100 obs → 200–400 words; 3,000+ → 800–1,300 words)
- Week 1 is the origin chapter; the final week closes with
## Where We Areinstead of a carry-forward, avoiding a false ending - Adds zero-padded numeric filename prefixes (
00-,01-…) for unambiguous sorting - Documented error handling for empty timelines, a stopped worker, and malformed or bloated carry-forward blocks
Who it's for
- Developers running claude-mem with weeks or months of accumulated observations
- Teams that want retros, release notes, or engineering history written engagingly
- Anyone who prefers chaptered serialization over one long
timeline-report - Advanced users studying sequential subagent orchestration patterns
Examples
- Long-running project (~30 weeks): "Make weekly digests for this project from beginning to end" → 30 chapters plus an index, with peak and trough weeks flagged in the final report.
- Three-week side project: chapter 1 establishes cast and tone, chapter 2 builds on its carry-forward, chapter 3 gets the final-chapter treatment.
- A quiet week: a week with only 20 observations still becomes a real chapter — silence is the story, naming what didn't happen rather than padding.
· · · Install guide · · ·
Install in the Claude app (no terminal)
- Download the ZIP with the button below.
- In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
- Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
Install in Claude Code
Let Claude do it — paste this into Claude Code
Install the skill I found on Claude Skill Mart. Copy the plugin/skills/weekly-digests folder from the GitHub repo thedotmack/claude-mem into my ~/.claude/skills/weekly-digests/. When it's done, tell me in one line what this skill can do.
Install with a command instead
git clone https://github.com/thedotmack/claude-mem.git /tmp/claude-mem && mkdir -p ~/.claude/skills && cp -r /tmp/claude-mem/plugin/skills/weekly-digests ~/.claude/skills/⚠ This is a third-party skill. Check the source repository before installing.
- Confirm the claude-mem plugin is installed and its worker is running — this skill depends on the worker's HTTP API.
- Clone the repository:
git clone https://github.com/thedotmack/claude-mem.git /tmp/claude-mem - Copy the skill folder:
mkdir -p ~/.claude/skills && cp -r /tmp/claude-mem/plugin/skills/weekly-digests ~/.claude/skills/ - Verify the file exists:
ls ~/.claude/skills/weekly-digests/SKILL.md - Restart Claude Code, open your project directory, and ask for "weekly digests" or a "week-by-week story" of the project.
- Output lands in
docs/timeline-weeks/anddocs/timeline-weeks/digests/— make sure that is a clean, writable location. - Expect long runtimes and heavy token use on multi-month projects; try a short project first to see the format.