playbooks

home / skills / nweii / agent-stuff / periodic-rollup

periodic-rollup skill

/skills/periodic-rollup

This skill consolidates vault content by rolling up periodic notes into histories and parent descriptions, preserving links and structure.

npx playbooks add skill nweii/agent-stuff --skill periodic-rollup

Review the files below or copy the command above to add this skill to your agents.

Files (4)
SKILL.md
2.0 KB
---
name: periodic-rollup
description: "Roll up vault content into consolidated notes. History rollup: compile periodic note mentions of a project/topic into a Histories note. Periodic rollup: synthesize child note descriptions into a parent periodic note's description."
argument-hint: "[[Project or topic]] [timespan] | [periodic note title]"
metadata:
  author: nweii
  version: "1.0.0"
  internal: true
---

# Vault rollups

Today's daily note: !`obsidian daily:path`

Two operations for aggregating periodic note content into consolidated artifacts. Determine which to run based on what's asked:

| Operation       | When to use                                                                            | Reference                                                      |
| --------------- | -------------------------------------------------------------------------------------- | -------------------------------------------------------------- |
| History rollup  | "Roll up history for [[Project]]", "compile mentions of [[Topic]]"                     | [references/history-rollup.md](references/history-rollup.md)   |
| Periodic rollup | "Roll up my weekly", "summarize this quarter", "generate description for [[2026-W07]]" | [references/periodic-rollup.md](references/periodic-rollup.md) |

If $ARGUMENTS is provided, use it to identify the project, topic, or periodic note to target. If ambiguous between the two operations, ask before proceeding.

## Shared workflow

Both operations follow the same pattern:

1. **Gather** — Search for source notes using obsidian CLI or MCP vault search
2. **Synthesize** — Process gathered content according to the operation's rules
3. **Write** — Produce or update the output note

## Shared principles

- Preserve source wikilinks back to origin notes for traceability
- Respect the hierarchy: daily → weekly → quarterly → yearly
- Preserve detail in archives; don't summarize what should be kept verbatim
- Update `related` properties bidirectionally when creating new notes

Overview

This skill consolidates scattered notes in a vault into coherent rollups. It supports two operations: History rollup, which compiles mentions of a project or topic across periodic notes into a single Histories note, and Periodic rollup, which synthesizes child periodic notes into a parent period description.

How this skill works

The skill gathers source notes via vault search or CLI, synthesizes content according to the chosen operation, and writes or updates the target note while preserving provenance. It maintains wikilinks back to origin notes, respects the daily→weekly→quarterly→yearly hierarchy, and updates related properties bidirectionally when creating or modifying notes.

When to use it

  • Compile a project's timeline or assemble mentions of a topic into a single History note
  • Generate or refresh a weekly, monthly, or quarterly period description from child notes
  • Create archive summaries while preserving links back to original entries for traceability
  • Run targeted rollups when given an explicit project/topic or a periodic-note identifier
  • Ask before proceeding if the target could be a History rollup or a Periodic rollup (ambiguous input)

Best practices

  • Provide an explicit argument (project, topic, or periodic note) to avoid ambiguity
  • Keep child notes focused and descriptive so synthesized descriptions remain useful
  • Preserve verbatim content for archive-worthy details; synthesize only summaries
  • Ensure your vault maintains consistent periodic naming (daily, weekly, quarterly)
  • Verify related properties are updated to maintain bidirectional navigation

Example use cases

  • Roll up history for 'Project Atlas' to create a single Histories note with links to every mention
  • Summarize the last four weekly notes into the current monthly note's description
  • Generate a quarterly overview by synthesizing weekly summaries and preserving source links
  • Refresh a yearly summary from quarterly rollups while keeping detailed entries intact
  • Aggregate meeting mentions across daily notes into a meeting-history page for reference

FAQ

What if the input is ambiguous between a project and a periodic note?

The skill will ask for clarification before proceeding to ensure the correct operation (History vs Periodic rollup).

Does the rollup delete or overwrite original notes?

No. Source notes are preserved; the rollup creates or updates consolidated notes and keeps wikilinks back to each origin.