Back to skills
SKILL.md
086 Meeting Intel 92b880fe
ASecurityProcess meetings from Granola to extract structured insights, action items, and update person pages.
- 9 stars
- 0 votes
- 0 copies
- 0 views
- Added October 11, 2026
Works with
Security analysis
100/100npx -y skills add tools-only/X-Skills --skill 086-meeting-intel_92b880fe --agent claude-codeAre you the author of 086 Meeting Intel 92b880fe?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/tools-only-086-meeting-intel-92b880fe)# Meeting Intelligence Reference
Process meetings from Granola to extract structured insights, action items, and update person pages.
## How It Works
Meetings sync **automatically in the background** every 30 minutes. No terminal commands shown during `/process-meetings`.
```
Granola App → Background Sync (every 30 min) → Synced Files → /process-meetings → Person Pages, Tasks
```
## Setup (One-Time, 30 Seconds)
```bash
cd .scripts/meeting-intel && ./install-automation.sh
```
**Requirements:**
- Granola app installed ([granola.ai](https://granola.ai))
- An LLM API key in `.env` (GEMINI_API_KEY, ANTHROPIC_API_KEY, or OPENAI_API_KEY)
**Check status:**
```bash
.scripts/meeting-intel/install-automation.sh --status
```
## Using /process-meetings
After setup, `/process-meetings` reads synced files and updates your vault:
```
/process-meetings # Process all synced meetings (last 7 days)
/process-meetings today # Just today's meetings
/process-meetings "Acme" # Find meetings by title/attendee
/process-meetings --setup # Install/check background automation
```
**Flags:**
- `--people-only` — Only update person/company pages (skip tasks)
- `--no-todos` — Create notes but don't extract tasks
- `--days-back=N` — Override default 7-day lookback
**What gets updated:**
- Person pages (05-Areas/People/) — meeting references, last interaction dates
- Company pages (05-Areas/Companies/) — key contacts, meeting history
- Tasks (03-Tasks/Tasks.md) — action items extracted from meetings
## What Gets Extracted
The background sync uses your LLM API to extract:
- **Summary** (2-3 sentences)
- **Key discussion points** with context
- **Decisions made**
- **Action items** (for you and others, with task IDs for sync)
- **Customer intelligence** (pain points, feature requests, competitive mentions)
- **Pillar classification** based on your `System/pillars.yaml`
**Output location:** `00-Inbox/Meetings/YYYY-MM-DD/meeting-slug.md`
## Configuration
Meeting intelligence is configured in `System/user-profile.yaml`:
```yaml
meeting_intelligence:
extract_customer_intel: true # Pain points, requests
extract_competitive_intel: true # Competitor mentions
extract_action_items: true # Always recommended
extract_decisions: true # Always recommended
```
Internal vs external classification uses your `email_domain` setting.
## Manual Sync (Optional)
To force a sync outside the 30-min schedule:
```bash
node .scripts/meeting-intel/sync-from-granola.cjs # Process now
node .scripts/meeting-intel/sync-from-granola.cjs --dry-run # Preview
node .scripts/meeting-intel/sync-from-granola.cjs --force # Reprocess today
```
## Stopping Background Sync
```bash
.scripts/meeting-intel/install-automation.sh --stop
```
## Logs
- `.scripts/logs/meeting-intel.log` - Processing log
- `.scripts/logs/meeting-intel.stdout.log` - Standard output
- `.scripts/logs/meeting-intel.stderr.log` - Errors
## Troubleshooting
**No meetings showing up?**
1. Make sure Granola is running during meetings
2. Check if background sync is set up: `./install-automation.sh --status`
3. Check logs for errors: `tail -50 .scripts/logs/meeting-intel.stderr.log`
**Background sync not running?**
```bash
cd .scripts/meeting-intel && ./install-automation.sh
```
**Want to re-process meetings?**
```bash
node .scripts/meeting-intel/sync-from-granola.cjs --force
```
Attribution
Comments
Loading comments…