Use when the user asks about meetings, meeting history, decisions made in meetings, action items from discussions, or what was discussed. Triggers on phrases like "what was decided", "meeting about", "action items from", "what happened in the meeting", "meeting notes", "transcript", "who attended", or when needing context from past conversations and discussions.
Retrieves meeting details, decisions, action items, and transcripts from past discussions.
npx claudepluginhub gleanwork/claude-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
When users need information from meetings - past discussions, decisions, action items, or transcripts - use Glean's meeting lookup.
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.
Use this approach when users ask:
Use the Glean meeting_lookup tool with natural language queries.
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"
Use natural language for dates:
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 valuesFilters that do work:
participants:"name" - Filter by attendeestopic:"subject" - Filter by meeting topicextract_transcript:"true" - Include transcript contentAdd extract_transcript:"true" when you need:
Skip transcripts for:
When analyzing meeting content, focus on:
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 moreExpert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.