# Daily Meeting Prep & Notes Processing: Your Setup Guide

**Author:** Matthew Jorat (joratm@)
**Last Updated:** May 1, 2026
**Status:** Verified working on Amazon Quick Desktop (macOS). Windows notes included below.

> Two companion skills that bookend your customer meetings: **Daily Meeting Prep** researches and generates structured prep files before meetings, and **Process Meeting Notes** cleans up your raw notes after meetings into structured outcomes. Together, they create a complete meeting lifecycle workflow.

---

## What You Get

| Skill | Trigger | What It Does |
|-------|---------|-------------|
| **Daily Meeting Prep** | `run meeting prep skill` | Pulls your calendar, identifies customer-facing meetings, researches each across AWSentral, Outlook email, Slack, local files, SIFT, and Knowledge Graph — then generates a thorough prep document per meeting |
| **Process Meeting Notes** | `process meeting notes` | Scans your prep files for raw notes, merges in Zoom meeting summary emails, and transforms everything into structured Meeting Outcomes |

**Bonus features** (on demand, after prep completes):
- 🎯 **Slide deck generation** — "Create a deck for the Kafka meeting" → 4-5 slide .pptx tailored to the meeting type
- 🔍 **LinkedIn contact lookup** — "Look up Jason Zondor" → searches LinkedIn for customer contacts with company/title context

---

## Prerequisites

| Requirement | How to Check | Why It's Needed |
|---|---|---|
| **Amazon Quick Desktop** | You're reading this in Quick | Runs the skills |
| **Outlook connected** | Settings → Capabilities → Connections → Outlook (green checkmark) | Calendar, email search, meeting summaries |
| **Slack connected** | Settings → Capabilities → Connections → Slack (green checkmark) | Channel search, message history, team context |
| **AWSentral MCP installed** | Ask Quick: "check if AWSentral is connected" — should return your SFDC info | SFDC opps, account metrics, spend data, SIFT, contacts |
| **At least one local folder added** | Settings → Capabilities → Local Files | Local document search, prep file storage |

**Optional but recommended:**
- **Builder MCP** — enables phonetool lookups for internal attendee info. If unavailable, the skills skip phonetool gracefully.
- **Knowledge Graph populated** — the more sources connected, the richer the KG context. The skills work without it, but customer lookups are faster and more complete with it.

### If AWSentral MCP isn't installed

Follow the [AWSentral MCP Setup Guide](https://amazon-my.sharepoint.com/:w:/p/peterkru/awsentral-mcp-setup) or ask in [#amazon-quick-desktop-beta-feedback](https://amazon.enterprise.slack.com/archives/C0ASRR957GU).

Quick version:
```bash
toolbox install aim && aim mcp install aws-sentral-mcp
```
Then add it in Settings → Capabilities → MCP with the full binary path (`which aws-sentral-mcp`).

---

## Installation

Both skills should already be installed if you received this guide. To verify:

> Ask Quick: **"What skills do you have for meeting prep?"**

You should see both `daily-meeting-prep` and `process-meeting-notes` in the response. If not, the skills need to be installed — ask whoever shared this guide for the SKILL.md files.

---

## Phase 1: Your First Meeting Prep (~2 minutes to trigger, ~5-10 minutes to run)

### Try it now

Say any of these:

- **"Run meeting prep skill"** — preps all customer-facing meetings for today
- **"Prep my meetings for tomorrow"** — specify a different date
- **"Prep for Love's"** — target a specific customer
- **"Prep SGWS meetings for Thursday"** — combine customer + date

### What happens behind the scenes

1. ✅ **Connector check** — verifies Outlook, AWSentral, and Slack are responsive
2. 📅 **Calendar pull** — finds your customer-facing meetings, filters out PTO/enablement/declined
3. 🔍 **Customer lookup** — checks the Knowledge Graph for SFDC Account ID, then falls back to a reference file, then AWSentral search
4. 🔬 **Deep research** — for each customer: SFDC opps, account metrics, spend by service, SIFT entries, activity history, email (10 threads deep), Slack, local files, Knowledge Graph relationships
5. 📝 **Prep file generation** — one markdown file per meeting with 14 sections
6. 📂 **Delivery** — opens all prep files in session tabs + offers deck/LinkedIn options

### What you'll see

Each prep file has these sections (lead with actionable, data pushed below):

1. Meeting Info
2. ⚡ TL;DR (3-4 sentences + relationship health ↗️/→/↘️)
3. Attendees (with roles, org info)
4. Since Last Meeting
5. Recommended Discussion Topics (format varies by meeting type)
6. Open Questions / Risks
7. Time-Sensitive Items
8. Email Thread Summaries (10 threads)
9. Slack Highlights (10 messages)
10. Account Snapshot (spend, health, pipeline)
11. Recent SIFT Insights
12. SFDC Pipeline
13. Recent Account Team Activity
14. Cross-Referenced Insights & Gaps

At the bottom: `## My Notes` — this is where you jot notes during the meeting.

---

## Phase 2: During Your Meeting

**Jot notes directly in the prep file.** Open the session tab, scroll to `## My Notes` at the bottom, and type. Shorthand is fine — abbreviations, fragments, image references, bullet soup. The notes processing skill is designed to handle messy input.

Examples of what works:
```
- JE wants POC for MSK, needs to loop in SA
- agreed $50k, next step: SOW by Friday  
- McManus asked about credit distribution timeline
- SKIP: don't bring up layoffs
- AI: Eric to send pricing comparison by EOW
```

---

## Phase 3: After Your Meeting (~1-2 minutes)

### Process your notes

Say any of these:

- **"Process meeting notes"** — processes all of today's prep files that have notes
- **"Process notes for Love's"** — target a specific customer
- **"Process meeting notes for yesterday"** — specify a different date

### What happens

1. 📂 **Finds prep files** matching the date
2. 🔍 **Detects raw notes** — reads from `## My Notes` to end of file. Even a single line counts.
3. 📧 **Searches for Zoom meeting summary** — looks for "Amazon Meetings Summary" emails matching the meeting name. Checks deleted items too (you probably archived it after reading).
4. 🔄 **Merges notes + email summary** — your notes are primary, email fills gaps
5. ✏️ **Updates the prep file in place** — replaces `## My Notes` with structured `## Meeting Outcomes`:
   - Discussion Summary (narrative, not bullets)
   - Attendees Present (who actually showed up)
   - Decisions Made
   - Action Items (table: Owner | Action | Due Date)
   - Open Questions
   - SFDC Updates Needed
6. 💾 **Saves a SharePoint copy** (if the customer's SharePoint folder is configured)

### No notes? No problem.

If you forgot to take notes but the meeting happened, the skill checks for a Zoom meeting summary email. If it finds one, it processes that instead. If neither exists, it skips the file silently.

---

## Phase 4: On-Demand Features

These are available anytime after prep files are generated:

### Slide Deck

> **"Create a deck for the Kafka meeting"**

Generates a 4-5 slide .pptx tailored to the meeting type:
- **External meetings**: Title → Agenda → Topic Overview (with web research) → Customer Use Cases → Next Steps
- **Weekly cadence**: Title → This Week's Focus → Workstream Status → Prior Decisions → Open Items
- **Internal team**: Title → Agenda → Account Context → Discussion Points → Action Items
- **Executive/QBR**: Title → Exec Summary → Account Health → Strategic Priorities → Asks

Content comes from your prep file. For external topic meetings (like a Kafka deep dive), the skill also runs a quick web search to enrich the topic slides with AWS capabilities and industry stats.

### LinkedIn Lookup

> **"Look up Jason Zondor"** or **"Who is Casey Hart at Love's?"**

Searches LinkedIn using the person's name + company (from the prep file). If the name is common, adds title and location to narrow results. Only works for external contacts — internal Amazon employees are looked up via the Knowledge Graph or phonetool instead.

⚠️ LinkedIn requires you to be signed in via browser. If Quick hits a login wall, it'll ask you to sign in and then retry.

---

## Customization: Customer Reference

The skills use a **hybrid lookup** to find customer metadata (SFDC Account ID, SharePoint path, Slack channel):

1. **Knowledge Graph** (primary) — enriched with your account data
2. **customerinfo.md** (fallback) — a reference file you maintain
3. **AWSentral search** (last resort) — dynamic but slower

To get the most out of the skills, populate your customer data in the Knowledge Graph. Ask Quick:

> **"Show me what's in the Knowledge Graph for Love's"**

If the SFDC Account ID is missing, you can add it:

> **"Add the SFDC Account ID 0015000000cAVcJAAW to the Love's entity in the Knowledge Graph"**

Or maintain a `customerinfo.md` file with a table of customer names, SFDC IDs, and SharePoint paths. The skills check for this file automatically as a fallback.

---

## Windows Installation

The skills themselves are platform-agnostic — they run inside Amazon Quick Desktop, which is available on both macOS and Windows. The main difference is how the **AWSentral MCP** dependency gets installed.

### What works the same on Windows

- Amazon Quick Desktop installation and setup
- Outlook and Slack connector configuration (Settings → Connections)
- Local folder access (Settings → Local Files)
- Both skills (`daily-meeting-prep` and `process-meeting-notes`) — no changes needed
- Slide deck generation and LinkedIn lookups

### What's different on Windows

**AWSentral MCP installation**: As of May 2026, the `aim mcp install` command is **not yet supported on Windows** natively. Workarounds:

1. **WSL (Windows Subsystem for Linux)** — Install the MCP binary inside WSL, then configure Amazon Quick to point to it:
   ```bash
   # Inside WSL terminal:
   toolbox install aim && aim mcp install aws-sentral-mcp
   which aws-sentral-mcp   # Note this path
   ```
   In Quick's MCP config, use the WSL path (e.g., `wsl.exe -- /home/<alias>/.toolbox/bin/aws-sentral-mcp`). This is not officially documented — check [#amazon-quick-desktop-beta-feedback](https://amazon.enterprise.slack.com/archives/C0ASRR957GU) for the latest Windows workarounds.

2. **Wait for remote MCP** — The Quick team is working on server-side (remote) MCP support for AWSentral, which eliminates the local install entirely. Once available, Windows users won't need local Toolbox/AIM at all.

**Builder MCP**: Also macOS-only via Toolbox. On Windows, phonetool lookups for internal attendees will be skipped (the skills handle this gracefully). Once remote MCP ships, this limitation goes away.

**Browser/LinkedIn lookups**: Work on Windows, but the browser skill uses Chrome's remote debugging protocol. Ensure Chrome is installed and not running with `--remote-debugging-port` already in use.

### Windows-specific troubleshooting

- **MCP shows "Error" after setup**: Ensure the WSL path is correct and that `mwinit` has been run inside WSL for Midway credentials.
- **Shell timeout**: Windows shell startup can be slower than macOS. Use the full binary path in the MCP command field, not a bare command name.
- **File paths**: Windows uses backslashes (`\`) but Quick normalizes to forward slashes internally. Local folder paths should work as-is from the Windows file picker in Settings.

---

## Troubleshooting

### "No customer-facing meetings found"

The skill filters aggressively. It skips: internal enablement, PTO, canceled meetings, declined meetings, and all-day events. If a meeting you expected was skipped:
- Check that the meeting title or attendees reference a customer
- Check that you haven't declined it
- Try targeting it directly: "Prep for [meeting title]"

### Email search returns nothing

The skill searches broadly (company name, domain, contact names, meeting topic) across all folders including deeply nested ones. If still empty:
- Run `mwinit` to refresh Outlook credentials
- Check Settings → Connections → Outlook is still green
- The skill can't access shared mailboxes — only your personal mailbox

### AWSentral calls fail with "AccessDenied"

Some SFDC accounts require explicit permission. The skill notes this and continues with other sources. If you need access, ask your manager or the account owner to grant it in Salesforce.

### Prep takes too long (>15 minutes for one customer)

The skill targets ~5 minutes per customer. If it's slow:
- Outlook throttling is the usual cause — the skill automatically retries
- For days with 5+ meetings across multiple customers, the skill parallelizes by spawning one background task per customer

### Meeting summary email not found

Zoom meeting summaries are sent after calls end. If the meeting just happened, wait 5-10 minutes for the email to arrive. The skill also checks your deleted items folder — meeting summaries are often read-and-deleted.

---

## The Full Workflow (Daily Habit)

```
Morning:   "Run meeting prep skill"           → prep files open in tabs
           Review prep files, note key talking points
           
Meeting:   Jot notes in ## My Notes section   → shorthand is fine

Optional:  "Create a deck for [meeting]"       → slide deck for specific meetings
           "Look up [person name]"             → LinkedIn background on customer contacts
```

Build this into your daily rhythm. The prep skill works best when you run it 30-60 minutes before your first customer meeting — it gives you time to review and absorb the context.

---

## Tips from Experience

1. **Run prep the night before** if you have early morning meetings. The skill works for any date: "Prep my meetings for tomorrow."

2. **The `## My Notes` section is editable in the session tab.** Click into it and type during the meeting. No need to switch apps.

3. **Group your meetings by customer** when reviewing. The skill generates one file per meeting, but if you have 3 Love's meetings, the research is shared — just flip between tabs.

4. **Don't worry about perfect notes.** The process skill handles shorthand, abbreviations, and fragments. Write what you'd write in a paper notebook.

5. **The Knowledge Graph gets better over time.** The more you use Quick (Slack, email, calendar), the more context it has. Your first prep run will be good. Your tenth will be great.

---

*Questions or issues? Reach out to joratm@ or post in [#amazon-quick-desktop-beta-feedback](https://amazon.enterprise.slack.com/archives/C0ASRR957GU).*