agentleFS
itseffiitseffi/agentic-os/.agents/skills/granola-meeting-sync/SKILL.md

granola-meeting-sync

Skill114 starsChanged 10 months agoMITView on GitHub

Sync new Granola meetings to local Knowledge folder. Use during daily planning, when user asks "what should I do today", or asks to review/sync meetings.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check for new Granola meetings and offer to sync them to your local Knowledge/transcripts folder.

    line 8
  2. Very specific:

    Call the check_new_meetings tool via the Granola MCP to see unsynced meetings.

    line 14
  3. Distinctive:

    If new meetings are found, present them to the user:

    line 18
  4. Distinctive:

    Ask the user to choose one option:

    line 32
  5. Very specific:

    Call sync_meeting_to_local with the meeting ID

    line 43
  6. Distinctive:

    After syncing (or skipping), continue with the normal daily planning workflow:

    line 48
  7. Distinctive:

    Only Granola meetings with notes/content are worth syncing

    line 68
  8. Distinctive:

    Use this skill when the task directly matches the workflow described above.

    line 75
  9. Distinctive:

    Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.

    line 79

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Meeting Sync

Check for new Granola meetings and offer to sync them to your local Knowledge/transcripts folder.

Instructions

Step 1: Check for New Meetings

Call the check_new_meetings tool via the Granola MCP to see unsynced meetings.

Step 2: Present Results

If new meetings are found, present them to the user:

I found X new meeting(s) since your last sync:

1. **Meeting Title** (Date)
2. **Meeting Title** (Date)
...

Add to Knowledge folder?

Step 3: Ask User for Selection

Ask the user to choose one option:

OptionDescription
Sync allAdd all new meetings to Knowledge/transcripts
Select specificLet user choose which meetings to sync
Skip for nowContinue without syncing

Step 4: Sync Selected Meetings

For each meeting the user wants to sync:

  1. Call sync_meeting_to_local with the meeting ID
  2. Confirm each sync completed

Step 5: Continue with Daily Flow

After syncing (or skipping), continue with the normal daily planning workflow:

  • Check tasks
  • Review priorities
  • Suggest focus items for the day

Example Flow

User: "What should I do today?"

Agent:

  1. Calls check_new_meetings
  2. "I found 3 new meetings since your last sync..."
  3. Asks the user which meetings to sync
  4. User selects "Sync all" or specific meetings
  5. Syncs selected meetings
  6. "Synced 3 meetings. Now for your day..."
  7. Continues with task planning

Notes

  • Only Granola meetings with notes/content are worth syncing
  • Meetings marked "(no notes)" may be empty placeholders
  • Sync state is tracked in Knowledge/.granola-sync.json
  • Files are saved to Knowledge/transcripts/ with sanitized filenames

When to Use

Use this skill when the task directly matches the workflow described above.

When Not to Use

Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.