Agent skill

granola-sync

Syncs Granola meeting notes to Obsidian vault. Reads from Granola's local cache to extract meeting metadata and notes, then creates properly formatted markdown files with frontmatter. Also handles manual transcript formatting when cache doesn't have content.

View SKILL.md on GitHub Repository
Stars 163
Forks 31

Install this agent skill to your Project

npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/granola-sync

SKILL.md

Granola Sync

When To Activate

Manual formatting:

  • User pastes a meeting transcript
  • User shares Granola export content
  • User says "format this meeting" with pasted content

Important Limitation

When local cache has no notes, ask user to copy from Granola app.

Instructions

Granola Cache Location

~/Library/Application Support/Granola/cache-v3.json

Cache Structure

json
{
  "cache": "{\"state\":{\"documents\":{...}}}"  // nested JSON string
}

Each document contains:

  • id - unique meeting ID
  • title - meeting title
  • notes_markdown - notes content (often empty)
  • notes_plain - plain text version
  • google_calendar_event.start.dateTime - meeting time
  • google_calendar_event.attendees - list with email fields

Reading the Cache

<read_cache>

bash
cat ~/Library/Application\ Support/Granola/cache-v3.json | python3 -c "
import json,sys
d=json.load(sys.stdin)
cache=json.loads(d['cache'])
docs=cache['state']['documents']

# List meetings with notes
for doc in docs.values():
    md = doc.get('notes_markdown', '')
    if md and len(md) > 50:
        title = doc.get('title', 'Untitled')
        cal = doc.get('google_calendar_event') or {}
        start = cal.get('start') or {}
        dt = start.get('dateTime', '')[:10]
        print(f'{dt} | {title[:40]} | {len(md)} chars')
"

</read_cache>

Output File Format

<file_format> Filename: YYYY-MM-DD-kebab-case-title.md Location: Project meetings folder (e.g., Projects/project-name/meetings/)

markdown
---
type: meeting
project: <project-name>
status: active
date: YYYY-MM-DD
attendees:
  - name1
  - name2
source: granola
granola-id: <meeting-id>
tags:
  - meeting
---

# Meeting Title

**Date**: YYYY-MM-DD
**Attendees**: Name1, Name2

---

## Notes

<notes_markdown content>

</file_format>

Manual Transcript Formatting

<manual_format> When user pastes a transcript without cache data:

  1. Ask for metadata if not obvious:

    • Meeting date
    • Attendees
    • Topic/title

  2. Structure the content:

markdown
---
type: meeting
project: <project>
status: active
date: YYYY-MM-DD
attendees:
  - name1
  - name2
source: granola-manual
tags:
  - meeting
---

# Topic Name

**Date**: YYYY-MM-DD
**Attendees**: Name1, Name2

---

## Summary

<2-3 sentence summary>

## Key Decisions

- Decision 1
- Decision 2

## Discussion Notes

<cleaned transcript, organized by topic>

## Action Items

- [ ] Action 1 (owner)
- [ ] Action 2 (owner)

</manual_format>

Output Format

When syncing from cache:

markdown
📥 **Granola Sync**

Found X meetings with notes:
- YYYY-MM-DD: Meeting Title (XXX chars)

Syncing to `Projects/project/meetings/`...

✓ Created: 2025-01-28-meeting-title.md

When no notes in cache:

markdown
📥 **Granola Sync**

Found X meetings but none have local notes cached.
Paste transcript content and I'll format it.

NEVER

  • Sync meetings without notes content
  • Overwrite existing meeting files without asking
  • Include sensitive attendee details beyond names
  • Create duplicate files for same meeting

ALWAYS

  • Use kebab-case lowercase filenames
  • Add frontmatter with proper metadata
  • Check for existing files before creating
  • Ask which project folder to use if unclear
  • Include granola-id to prevent duplicates

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

majiayu000/claude-skill-registry

agent-ops-spec

Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.

163 31
Explore
majiayu000/claude-skill-registry

agent-ops-state

Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.

163 31
Explore
majiayu000/claude-skill-registry

agent-ops-spec

Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.

163 31
Explore
majiayu000/claude-skill-registry

agent-ops-testing

Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.

163 31
Explore
majiayu000/claude-skill-registry

agent-ops-testing

Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.

163 31
Explore
majiayu000/claude-skill-registry

agent-ops-state

Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.

163 31
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results