meeting-context

Meeting Context via Glean

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "meeting-context" with this command: npx skills add gleanwork/claude-plugins/gleanwork-claude-plugins-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 ignored

  • after:YYYY-MM-DD

  • ISO dates return no results

  • after:yesterday

  • Simple keywords don't work as filter values

Filters that do work:

  • participants:"name"

  • Filter by attendees

  • topic:"subject"

  • Filter by meeting topic

  • extract_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

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

project-awareness

No summary provided by upstream source.

Repository SourceNeeds Review
General

glean-tools-guide

No summary provided by upstream source.

Repository SourceNeeds Review
General

activity-synthesis

No summary provided by upstream source.

Repository SourceNeeds Review