meeting-context
Meeting Context via Glean
When users need information from meetings - past discussions, decisions, action items, or transcripts - use Glean's meeting lookup.
Tool Naming
See the glean-tools-guide skill for Glean MCP tool naming conventions. Tools follow the pattern mcp__glean_[server-name]__[tool] where the server name is dynamic. Use whatever Glean server is available in your tool list.
When This Applies
Use this approach when users ask:
- "What was decided in the [topic] meeting?"
- "What action items came out of [meeting]?"
- "When did we discuss [topic]?"
- "What meetings did I miss [time period]?"
- "Who attended [meeting]?"
- "What was said about [topic] in recent meetings?"
Primary Tool
Use the Glean meeting_lookup tool with natural language queries.
Query Syntax
Important: meeting_lookup works best with natural language queries. Date filter syntax does NOT work reliably.
# By topic and time (natural language)
meeting_lookup "quarterly planning last week"
# With specific participants
meeting_lookup "standup with John Smith"
meeting_lookup "participants:\"John Smith\" topic:\"standup\""
# Get transcript content
meeting_lookup "team sync last week extract_transcript:\"true\""
# Today's meetings
meeting_lookup "my meetings today"
# Past week
meeting_lookup "meetings past week"
Date Filtering
Use natural language for dates:
- "last week", "past 2 weeks", "yesterday", "today", "tomorrow"
- "meetings since Monday", "standups this month"
Inline date filters do NOT work reliably:
after:now-1w- Date math is ignoredafter:YYYY-MM-DD- ISO dates return no resultsafter:yesterday- Simple keywords don't work as filter values
Filters that do work:
participants:"name"- Filter by attendeestopic:"subject"- Filter by meeting topicextract_transcript:"true"- Include transcript content
When to Extract Transcripts
Add extract_transcript:"true" when you need:
- Specific quotes or statements
- Detailed discussion content
- Action item context
- Decision rationale
Skip transcripts for:
- Just listing meetings
- Checking attendees
- Quick time/date lookup
What to Extract from Meetings
When analyzing meeting content, focus on:
- Decisions made - What was agreed? By whom?
- Action items - Tasks assigned, owners, deadlines
- Open questions - Unresolved items
- Key discussion points - Important debates or context
Relationship to Commands
For comprehensive meeting workflows, suggest:
/glean-meetings:meeting-prep <meeting>- Prepare for an upcoming meeting/glean-meetings:catch-up <period>- Catch up on missed meetings and more
More from gleanwork/claude-plugins
code-exploration
Use when the user asks about internal code, implementations, patterns across repositories, or needs to understand how something is built. Triggers on "how is X implemented", "where is the code for", "find the implementation of", "what repos contain", "who wrote the code for", or code architecture questions about internal systems.
15glean-tools-guide
Use when Glean MCP tools are available and you need guidance on which tool to use, how to format queries, or best practices for enterprise search. This skill provides tool selection logic and query optimization for Glean integrations. Auto-triggers when mcp__glean tools are being considered.
14activity-synthesis
Use when the user asks about their recent work, what they've been doing, their contributions, or needs to recall past activity. Triggers on phrases like "what have I been working on", "what did I do last week", "my recent activity", "what have I accomplished", "summarize my work", "what projects am I on", or when the user needs to recall or reflect on their own work.
13project-awareness
Use when the user asks about project status, ownership, or context. Triggers on phrases like "status of X project", "who owns Y", "what's happening with Z", "project update", "where does the project stand", "what's the state of", "who's working on", or when needing quick project context without a full analysis.
13people-lookup
Use when the user asks about people, employees, team members, org structure, or expertise. Triggers on phrases like "who works on", "who is responsible for", "who owns", "find someone who knows", "who should I talk to", "who reports to", "team members", "org chart", or any question starting with "who" about the company.
12enterprise-search
Use when the user asks about company documents, internal wikis, policies, specifications, design docs, RFCs, or enterprise knowledge. Triggers on phrases like "find the doc about", "what's our policy on", "where is the spec for", "company guidelines", "internal documentation", or when searching for information that would be in enterprise systems rather than the local codebase.
12