sync-meetings

Dependency Check

Before starting, verify required dependencies:

1. Granola MCP (required): Check if Granola MCP tools are available in your tools list.
   • If missing: Tell the user: "The Granola MCP server is not configured. This skill requires Granola MCP. Please install and configure the Granola MCP server (see https://granola.ai) and try again." Stop here.

Context

Sync state is tracked in <target-folder>/.synced-meetings.json. Today's date: $TODAY Arguments: $ARGUMENTS

Your Task

Sync Granola meetings to <target-folder> using the Granola MCP.

---

Step 1: Parse Arguments

• First positional arg = target folder (default: meetings/)
• --days N = sync meetings from the last N days
• --all = re-sync all meetings, ignoring sync state

Step 2: Check Sync State

Read <target-folder>/.synced-meetings.json. If it doesn't exist, this is a first sync.

{
  "last_sync": "<ISO timestamp>",
  "synced": {
    "<meeting-uuid>": {
      "title": "Meeting Title",
      "synced_at": "<ISO timestamp>",
      "file_path": "meetings/2026-03-16-Meeting-Title.md"
    }
  }
}

Step 3: List Meetings from Granola

Via Granola MCP, list meetings with the appropriate time range:

• First sync (no .synced-meetings.json): use last_30_days
• Subsequent syncs: use this_week
• --days N: use custom range based on N
• --all: use last_30_days and ignore existing sync state

Step 4: Filter Unsynced Meetings

Compare returned meeting IDs against the synced keys in .synced-meetings.json.

• Skip any meeting whose ID is already synced (unless --all was passed)
• Build a list of unsynced meetings with title + date

Step 5: Present to User

Show the list of unsynced meetings:

Found N new meetings to sync:
1. 2026-03-18 — Weekly Standup
2. 2026-03-17 — Product Review
3. 2026-03-16 — 1:1 with Manager

Sync all, select specific (e.g. "1,3"), or skip?

Wait for user confirmation before proceeding.