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 |
examples/customer-meeting.md
View on GitHub# Example: Customer Meeting Prep
**User Request**: "Prep for sales meeting with Acme Corp on Thursday"
## Workflow
### 1. Search Customer Info
```
Notion:notion-search
query: "Acme Corp"
```
Found:
- CRM notes from initial call
- Product demo feedback
- Pricing proposal
- Competitor analysis
### 2. Fetch Details
```
Notion:notion-fetch (4 pages)
```
**Key context**:
- **Company**: 500-person fintech startup, Series B
- **Pain Points**: Manual workflows, data silos, scaling issues
- **Decision Makers**: CTO (technical), VP Product (user needs), CFO (budget)
- **Timeline**: Need solution by Q1
- **Budget**: $50-75K/year range
- **Competition**: Evaluating us vs. Competitor A and Competitor B
### 3. Add Research Context
Claude research added:
- Fintech industry compliance requirements
- Common integration needs for financial products
- Typical procurement processes for Series B companies
### 4. Create Internal Pre-Read
```
Notion:notion-create-pages
pages: [{
properties: {
title: "Acme Corp Meeting - Pre-Read (Internal)"
},
content: "# Acme Corp Meeting - Pre-Read (Internal)
## Company Overview
**Company**: Acme Corp (500-person fintech, Series B)
**Decision Makers**: CTO, VP Product, CFO
Source: <mention-page url='...'>CRM Notes</mention-page>
## Their Pain Points → Our Solutions
- Manual workflows → Workflow automation
- Data silos → API integrations
- Scaling issues → Enterprise features
## Competitive Position
**Our advantages over Competitor A/B**:
- Better integration ecosystem (Stripe, Plaid)
- Stronger compliance features
- Faster implementation (4 weeks vs 12 weeks)
## Pricing Strategy
Recommend: $60K/year (mid-range of their budget)
## Potential Objections & Responses
..."
}]
```
### 5. Create Meeting Agenda
```
Notion:notion-create-pages
pages: [{
properties: {
title: "Acme Corp - Product Demo & Q&A"
},
content: "# Acme Corp - Product Demo & Q&A
## Meeting Details
**Date**: Thursday, Oct 17, 2025 @ 2pm PST
**Attendees**: CTO, VP Product, CFO (Acme) | Sales Lead, Solutions Engineer (Us)
**Duration**: 60 minutes
## Objective
Demonstrate how our platform solves Acme's workflow automation and integration challenges.
## Agenda
**1. Introductions** (5 min)
**2. Understand Current Workflow** (10 min)
- Current pain points
- Integration requirements
- Success criteria
**3. Product Demo** (25 min)
- Workflow automation capabilities
- API integrations (Stripe, Plaid)
- Security & compliance features
**4. Pricing & Implementation** (10 min)
**5. Next Steps** (10 min)
"
}]
```
### 6. Link Resources
Connected agenda to CRM page, pricing sheet, and technical integration docs.
## Outputs
**Internal Pre-Read**: Full context for sales team
**Customer Agenda**: Professional meeting structure
**Both in Notion** with links to supporting materials
## Key Success Factors
- Understood customer's specific pain points
- Researched industry context (fintech compliance)
- Mapped features to their needs
- Prepared competitive differentiators
- Structured demo around their use cases
- Pre-planned objection responses
- Clear next steps in agenda
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 |