cerebro-granola-archiver

Back up Granola meeting transcripts to an Obsidian vault by running a gap analysis for your target date range, fetching missing meetings in batches, creating vault files, and appending transcripts using the local shell script.

No, archiving Granola notes does not send transcript data through Claude's context. Transcripts are sourced directly from the local Granola cache via the shell script to maintain token efficiency.

Yes, you can archive Granola meeting summaries for a specific weekly range. The archival workflow supports custom date ranges, allowing targeted gap analysis and batch retrieval of missing meeting data.

The best way to automate meeting data preservation from Granola is using batched processing with local scripts. This approach runs gap analysis without subagents, retrieves missing summaries, and writes them directly to your vault.

No, you do not need subagents to retrieve Granola metadata and notes. The Skill satisfies token-efficiency rules by using batched processing and local scripts instead of subagents for the entire archival workflow.

Your Granola vault backup may skip certain meeting transcripts if gap analysis has not been run for that specific date range. Run a gap analysis first to identify and fetch missing meetings in batches before appending transcripts.