querying-granola
Queries local Granola meeting cache for meeting history, context, and attendee information. Use when preparing for meetings, researching past interactions with a person or company, finding past discussions on a topic, tracking engagement, or when user mentions Granola, meeting notes, meeting history, or attendees.
When & Why to Use This Skill
This Claude skill enables seamless access to your local Granola meeting cache, allowing you to retrieve meeting history, AI-generated summaries, and attendee information directly within your workflow. It streamlines meeting preparation and relationship management by providing instant context from past discussions, tracking engagement patterns across different domains, and identifying follow-up opportunities with stale contacts.
Use Cases
- Meeting Preparation: Quickly research past interactions, notes, and action items with a specific person or company before a scheduled call to ensure continuity.
- Engagement Tracking: Identify 'stale' accounts or domains that haven't had a meeting in over 60 days to prioritize outreach and re-engagement efforts.
- Knowledge Retrieval: Search through comprehensive AI-generated meeting summaries and transcripts to find specific technical decisions or project updates discussed in previous sessions.
- Relationship Mapping: Generate company profiles that list all contacts met, meeting frequency, and recent discussion history to understand the depth of an organizational relationship.
- Activity Analysis: Visualize meeting frequency over time using the timeline command to track team momentum or client engagement trends.
| name | querying-granola |
|---|---|
| description | Queries local Granola meeting cache for meeting history, context, and attendee information. Use when preparing for meetings, researching past interactions with a person or company, finding past discussions on a topic, tracking engagement, or when user mentions Granola, meeting notes, meeting history, or attendees. |
Querying Granola
Query the local Granola meeting cache. Requires Python 3.
Note: This reads from an unofficial local cache file, not a Granola API. The cache format could change with Granola updates.
Run this script to query meetings:
python3 skills/querying-granola/scripts/granola.py <command> [args]
Do not read the script source; execute it with the commands below.
Primary Commands (search by title/notes/attendee names)
| Command | Purpose |
|---|---|
client <name> |
Get meetings matching name in title, notes, or attendee names/emails |
search <query> |
Search by keyword in title, notes, or attendees |
context <title> |
Get full notes + transcript for a specific meeting |
Domain-Based Commands (require @domain.com in attendee list)
| Command | Purpose |
|---|---|
profile <domain> |
Company/org profile with contacts and meeting history |
active [N] |
Most active domains in last N days (default 30) |
stale [N] |
Domains with no meetings in N+ days (default 60) |
domains |
Meeting counts by email domain |
Other Commands
| Command | Purpose |
|---|---|
timeline <query> |
Meeting frequency over time (visual bar chart) |
recent [N] |
List N most recent meetings (default 20) |
people |
Meeting counts by person |
Workflows
Before a meeting
Progress:
- [ ] Run profile for company/person context
- [ ] Run search for recent meeting history
- [ ] Identify key topics and contacts
- [ ] Check for unresolved action items
profile domain.com→ contacts, meeting count, recent notessearch "PersonName"orclient "CompanyName"→ recent meeting notes- Review for action items, open questions
Engagement tracking
Progress:
- [ ] Check active domains for recent engagement
- [ ] Check stale domains for follow-up opportunities
- [ ] Review timeline for engagement patterns
active 30→ who you've been meeting with recentlystale 60→ contacts you haven't met with in a whiletimeline "name"→ meeting frequency over time
Output Examples
profile returns: meeting count, date range, contacts with meeting counts, recent meeting previews.
timeline returns: monthly bar chart showing meeting frequency with sample titles.
active/stale returns: domain, meeting count, top contacts.
Data Sources
The script extracts from multiple cache sections:
| Source | Contains |
|---|---|
documents |
Meeting title, date, user-typed notes, basic attendees |
documentPanels |
AI-generated summaries (comprehensive meeting notes) |
meetingsMetadata |
Enriched attendee info with company names |
transcripts |
Raw meeting transcripts (~8 recent meetings cached locally) |
Notes priority: AI summaries are preferred over user-typed notes when available (more comprehensive).
Company names: Displayed as Name <email> @ Company when enriched data exists.
Transcripts: Only available for recent meetings; displayed in context command when present.
Limitations
Domain-based commands (active, stale, profile) only work when attendee emails are captured in the meeting invite. If you join someone else's meeting link (their Zoom/Meet), their email may not be in your attendee list. Use search or client by name/title for these cases.
Transcripts are only cached locally for recent meetings (~8). Older meetings won't have transcript data available.