Agent skill · Data & Analytics

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.

Alex Newman88,857★ · +719/wk · 1 repos on radarProfile →
claude-codeApache-2.0
Install
npx skills add thedotmack/claude-mem --skill weekly-digests --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 14 KB
Bundled scripts: none
Path: plugin/skills/weekly-digests/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 89,517 · +660 this week
Language: JavaScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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`): ```bash WORKER_PORT="${CLAUDE_MEM_WORKER_PORT:-$(no

What's inside
Steps it walks through
  1. When to Use
  2. Prerequisites
  3. Workflow
  4. Step 1: Determine the Project Name
  5. Step 2: Fetch the Full Timeline and Save It
  6. Step 3: Split the Timeline Into Per-ISO-Week Files
  7. Step 4: Build the Weekly Index README
  8. Step 5: Run the Consecutive Subagent Pipeline
  9. Step 6: Rename Files for Sortable Order
  10. Step 7: Report Completion
  11. Pipeline Discipline
  12. Error Handling
  13. Examples
  14. Long-running project (~30 weeks)
Commands it runs
if [ "$git_dir" != "$git_common_dir" ]; then
else
fi
echo "$parent_project"
mkdir -p .scratch
curl -s "http://localhost:${WORKER_PORT}/api/context/inject?project=PROJECT_NAME&full=true" \
wc -l .scratch/cm-timeline.md
mkdir -p docs/timeline-weeks/digests
More from claude-mem
All skills →
About this skill
What does the weekly-digests skill do?

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.

How do I install it?

Run `npx skills add thedotmack/claude-mem --skill weekly-digests --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From thedotmack/claude-mem, a repository with 89,517 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going