prep-meetings
准备客户会议,从多个数据源汇总信息。使用/prep-meetings指令激活。
📖 中文导读:准备客户会议,从多个数据源汇总信息。使用/prep-meetings指令激活。 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。
name: prep-meetings description: Prepare for customer meetings by aggregating context from multiple data sources. Invoked with /prep-meetings.
Customer Meeting Prep
Generate concise meeting prep summaries by pulling context from multiple data sources.
Invocation
/prep-meetings- Prep for all customer meetings on today's calendar/prep-meetings <CustomerName>- Prep for a specific customer
Data Sources
This skill aggregates data from:
- Vitally - Account health, notes, CSM assignment
- Granola - Past meeting notes and transcripts
- Slack - Recent channel activity
- Linear - Open issues and feature requests
- Zendesk - Support tickets
- Grafana - Product usage metrics
Execution Flow
Step 1: Identify Customer
- From calendar: Extract domain from non-Socket attendee email
- From argument: Use provided customer name
Step 2: Match to Vitally Account
Search Vitally accounts by domain or name match.
Step 3: Fetch Data (Parallel)
Query all data sources simultaneously to minimize latency.
Step 4: Generate Summary
Output formatted prep document.
Output Format
═══════════════════════════════════════════════════════════════
MEETING PREP: {Customer Name}
Meeting: {Title} @ {Time}
═══════════════════════════════════════════════════════════════
ACCOUNT OVERVIEW
├─ ARR: ${amount}
├─ Renewal: {date} ({days} days)
├─ Products: {SCA, Firewall, Extension Guard}
├─ AE: {account_executive}
└─ Health: {score}
PRODUCT USAGE (Last 30 Days)
├─ Licensed Seats: {count}
├─ Active Committers: {count} ({utilization}%)
├─ Full Scans: {count}
└─ PR Scans: {count}
ALERTS
├─ Critical: {count}
├─ High: {count}
├─ Medium: {count}
└─ Low: {count}
RECENT NOTES
• {date}: {summary}
• {date}: {summary}
SLACK HIGHLIGHTS
• {key theme}
• {key theme}
OPEN LINEAR ISSUES ({count})
• {TEAM}-{id}: {title}
• {TEAM}-{id}: {title}
SUPPORT TICKETS ({count} in 30 days)
• #{id}: {subject} ({status})
LAST MEETING
{date}: {title}
Key points: {summary}
───────────────────────────────────────────────────────────────
Implementation Notes
- Parallel execution: Fetch from all sources simultaneously
- Graceful degradation: Show available data even if some sources fail
- Date formatting: Use relative dates ("3 days", "2 weeks")
- Summarization: Keep each section to 2-3 bullet points max