Prat011/awesome-llm-skills / notion-meeting-intelligence
notion-meeting-intelligence
UnverifiedPrepares meeting materials by gathering context from Notion, enriching with Claude research, and creating both an internal pre-read and external agenda saved to Notion. Helps you arrive prepared with comprehensive background and structured meeting docs.
| File | Kind | Size |
|---|---|---|
| .DS_Store | binary | 6.0 KB |
| SKILL.md | skill md | 11.0 KB |
| evaluations/.DS_Store | binary | 6.0 KB |
| evaluations/README.md | markdown | 3.9 KB |
| evaluations/decision-meeting-prep.json | config | 3.4 KB |
| evaluations/status-meeting-prep.json | config | 3.2 KB |
| examples/customer-meeting.md | markdown | 3.1 KB |
| examples/executive-review.md | markdown | 2.1 KB |
| examples/project-decision.md | markdown | 12.5 KB |
| examples/sprint-planning.md | markdown | 2.1 KB |
| reference/brainstorming-template.md | markdown | 1.4 KB |
| reference/decision-meeting-template.md | markdown | 1.8 KB |
| reference/one-on-one-template.md | markdown | 932 B |
| reference/retrospective-template.md | markdown | 940 B |
| reference/sprint-planning-template.md | markdown | 1.3 KB |
| reference/status-update-template.md | markdown | 1.3 KB |
| reference/template-selection-guide.md | markdown | 1.9 KB |
evaluations/README.md
View on GitHub# Meeting Intelligence Skill Evaluations
Evaluation scenarios for testing the Meeting Intelligence skill across different Claude models.
## Purpose
These evaluations ensure the Meeting Intelligence skill:
- Gathers context from Notion workspace
- Enriches with Claude research appropriately
- Creates both internal pre-reads and external agendas
- Distinguishes between Notion facts and Claude insights
- Works consistently across Haiku, Sonnet, and Opus
## Evaluation Files
### decision-meeting-prep.json
Tests preparation for a decision-making meeting.
**Scenario**: Prep for database migration decision meeting
**Key Behaviors**:
- Searches Notion for migration context (specs, discussions, options)
- Fetches 2-3 relevant pages
- Enriches with Claude research (decision frameworks, migration best practices)
- Creates comprehensive internal pre-read with recommendation
- Creates clean, professional external agenda
- Clearly distinguishes Notion facts from Claude insights
- Cross-links both documents
### status-meeting-prep.json
Tests preparation for a status update or review meeting.
**Scenario**: Prep for project status review
**Key Behaviors**:
- Gathers project metrics and progress from Notion
- Fetches relevant pages (roadmap, tasks, milestones)
- Adds Claude context (industry benchmarks, best practices)
- Creates internal pre-read with honest assessment
- Creates external agenda with structured flow
- Includes source citations using mention-page tags
- Time-boxes agenda items
## Running Evaluations
1. Enable the `meeting-intelligence` skill
2. Submit the query from the evaluation file
3. Verify the skill searches Notion first (not Claude research)
4. Check that TWO documents are created (internal + external)
5. Verify Claude enrichment adds value without replacing Notion content
6. Test with Haiku, Sonnet, and Opus
## Expected Skill Behaviors
Meeting Intelligence evaluations should verify:
### Notion Context Gathering
- Searches workspace for relevant context first
- Fetches specific pages (not generic)
- Extracts key information from Notion content
- Cites sources using mention-page tags
### Claude Research Integration
- Adds industry context, frameworks, or best practices
- Enrichment is relevant and valuable (not filler)
- Clearly distinguishes Notion facts from Claude insights
- Research complements (doesn't replace) Notion content
### Two-Document Creation
- **Internal Pre-Read**: Comprehensive, includes strategy, recommendations, detailed pros/cons
- **External Agenda**: Professional, focused on meeting flow, no internal strategy
- Both documents are clearly labeled
- Documents are cross-linked
### Document Quality
- Pre-read follows structure: Overview → Background → Current Status → Context & Insights → Discussion Points
- Agenda follows structure: Details → Objective → Agenda Items (with times) → Decisions → Actions → Resources
- Titles include date or meeting context
- Content is actionable and meeting-ready
## Creating New Evaluations
When adding Meeting Intelligence evaluations:
1. **Test different meeting types** - Decision, status, brainstorm, 1:1, sprint planning, retrospective
2. **Vary complexity** - Simple updates vs. complex strategic decisions
3. **Test with/without Notion content** - Rich workspace vs. minimal existing pages
4. **Verify enrichment value** - Is Claude research genuinely helpful?
5. **Check internal/external distinction** - Is sensitive info kept in pre-read only?
## Example Success Criteria
**Good** (specific, testable):
- "Creates TWO documents (internal pre-read + external agenda)"
- "Internal pre-read marked 'INTERNAL ONLY' or 'For team only'"
- "Cites at least 2-3 Notion pages using mention-page tags"
- "Agenda includes time allocations for each section"
- "Claude enrichment includes decision frameworks or best practices"
**Bad** (vague, untestable):
- "Creates meeting materials"
- "Gathers context effectively"
- "Prepares well"
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |