# Meeting Summarizer

> Shareable markdown export of `meeting-summarizer.skill` — exported 2026-08-25 from the MBAC Skills library.
>
> **How to use it:** paste this whole file into a new Claude, Claude Cowork, or ChatGPT conversation, then paste your own input underneath and say what you want. No install required. The `.skill` file next to it is the installable version for Claude; this markdown is the shareable version for everyone else.

**What it does:** Transform raw meeting notes, transcripts, or recordings into structured, actionable summaries with built-in accountability tracking. Automatically classifies the meeting as an MBAC Counseling Session, a Discovery Call, a Workshop or Event, an Internal meeting, or a Sales meeting, then applies the appropriate output template. Triggers on any request involving meeting notes, meeting summaries, meeting recaps, action items from meetings, call summaries, or post-meeting follow-up. Also triggers on "summarize my counseling session", "write up this discovery call", "recap the workshop", "session notes", "debrief the event", and when the user pastes or uploads a transcript, raw notes, or audio summary and asks to "summarize", "write up", "pull action items", or "create meeting notes". Use this skill for any meeting-related summarization or action-item extraction task.

---
## Overview

Transform raw meeting input into an actionable report that ensures follow-through and accountability. Every summary must answer: **Who owes what, by when?**

## Step 1 — Classify the Meeting

Determine meeting type from context clues in the notes. Ask the user only if genuinely ambiguous.

| Signal → Type | Examples |
|---|---|
| **MBAC Counseling Session** | An existing MBAC client, one-on-one, certification (MBE / EDGE / VFBE / WBE), access to capital, contracting, loan packaging, business plan review, "next session," referrals to partners or state programs |
| **Discovery Call** | A first conversation with a prospect, partner, or funder. "What do you do," "how does this work," qualifying questions, no counseling work done yet, ends in a booking or a decision to book |
| **Workshop / Event** | Group setting, registrations and attendance, presenter or panel, Q&A, a room rather than a person, post-event follow-up for attendees and no-shows |
| **Internal Meeting** | Team standup, planning, strategy, all-hands, 1-on-1, retrospective, no external party |
| **Sales Meeting** | Demo language, pricing, proposal references, a paid engagement, "their team / our team" framing, CRM or pipeline mentions |

**MBAC tie-breaker:** MBAC's services are no-cost. A conversation with a business owner is a **Counseling Session** if MBAC is already doing work for them, and a **Discovery Call** if the point of the call was to find out what they need and get them booked. If money changes hands, it is a Sales Meeting, not either of these.

If uncertain after scanning the notes, ask **one** clarifying question:

> "Which type is this — **Counseling Session**, **Discovery Call**, **Workshop**, **Internal**, or **Sales**?"

## Step 2 — Gather Minimum Viable Context

Before generating output, confirm you have these essentials. Ask **one question at a time** until 95 % confident you can produce the correct output. Do not ask for information already present in the notes.

**Required for both types:**
- Date of meeting (or approximate)
- Attendees / participants
- Raw notes, transcript, or summary

**Additionally required, by type:**

| Type | Also needed |
|---|---|
| **Counseling Session** | Client business name, the counselor who held the session, what the client came in for |
| **Discovery Call** | Prospect name and business, how they found MBAC, whether a session got booked |
| **Workshop / Event** | Event name and date, presenter(s), registered vs. attended counts |
| **Sales Meeting** | Client / prospect company name, what product or service was discussed |
| **Internal Meeting** | Nothing beyond the essentials above |

If all required info is present in the supplied notes, skip straight to output — do not interrogate the user unnecessarily.

## Step 3 — Generate the Summary

### A. MBAC Counseling Session Output

Matches MBAC Skill 03, Counseling Summary. This is the format that gets logged to the client record.

```
# Counseling Session Summary
**Date:** [date]
**Client:** [business name]
**Counselor:** [name]
**Session:** [First / Follow-up #n]

---

## What they came in for
[The client's own words. Do not translate it into program language.
If they said "I need to get certified so I can bid on the airport
job," write that, not "MBE certification support."]

## What we covered
[2-4 sentences: what was discussed and what was decided.]

## Action items
**What MBAC owes the client**
| # | Action | Owner | Due Date | Status |
|---|--------|-------|----------|--------|
| 1 | [task] | [name] | [date]   | Open   |

**What the client owes themselves**
| # | Action | Due Date | Status |
|---|--------|----------|--------|
| 1 | [task] | [date]   | Open   |

## Referrals made
- [Partner, program, or state resource + why]
(Omit section if none)

## Next touch
**[Date]** — [what happens, and who reaches out]
```

### B. Discovery Call Output

```
# Discovery Call Summary
**Date:** [date]
**Business:** [business name]
**Owner / contact:** [name, role]
**Source:** [landing page / workshop / referral / outreach sequence]

---

## Situation
[Three sentences. What the business is, where it is right now,
and why they picked up the phone.]

## What they need, in their words
- "[verbatim quote or near-verbatim phrasing]"
- "[...]"

## What MBAC can actually help with
- [Service 1 — certification / capital / contracting / counseling]
- [Service 2]

## Fit and readiness
[Are they eligible? Are they ready to do the work? What would
have to be true for this to go somewhere. Flag anything unclear.]

## Action items
| # | Action | Owner | Due Date | Status |
|---|--------|-------|----------|--------|
| 1 | [task] | [name] | [date]   | Open   |

## Next touch
**[Date]** — [booked counseling session, intake to complete,
or the sequence they go into]
```

### C. Workshop / Event Output

```
# Workshop Debrief
**Event:** [name]
**Date:** [date]
**Presenter(s):** [names]
**Registered / Attended:** [n] / [n]

---

## What we promised the room
[The walk-away promise from the promotion kit, in one sentence.]

## What actually landed
[2-4 sentences: what the room responded to, what fell flat,
what questions kept coming up.]

## Questions and needs raised
- [Question or need 1 — and who raised it, if known]
- [Question or need 2]

## Follow-up routing
| Group | Count | Next action | Owner | Due Date |
|-------|-------|-------------|-------|----------|
| Attendees | [n] | Day-after follow-up to intake landing page | [name] | [date] |
| No-shows  | [n] | "Sorry we missed you" + intake link | [name] | [date] |
| Hot leads | [n] | Book a counseling session directly | [name] | [date] |

## Action items
| # | Action | Owner | Due Date | Status |
|---|--------|-------|----------|--------|
| 1 | [task] | [name] | [date]   | Open   |

## What to change next time
- [Fix 1]
- [Fix 2]
```

### D. Sales Meeting Output

```
# Sales Meeting Summary
**Date:** [date]
**Client:** [company name]
**Attendees:** [names + roles if available]
**Meeting Stage:** [Discovery / Demo / Proposal / Negotiation / Follow-Up]

---

## Unique Proposition Statement
[One sentence capturing the single most compelling value proposition
presented or implied during this meeting. Frame it from the client's
perspective: what specific outcome or transformation was offered.]

## Client Needs (as discussed)
- [Need 1 — stated in the client's own language where possible]
- [Need 2]
- [Need 3]
- [...additional needs]

## Key Discussion Points
[2-4 sentence narrative of the most important topics covered]

## Objections / Concerns Raised
- [Objection 1 + how it was addressed, if at all]
- [Objection 2]
(Omit section if none surfaced)

## Action Items
| # | Action | Owner | Due Date | Status |
|---|--------|-------|----------|--------|
| 1 | [task] | [name] | [date]   | Open   |
| 2 | [task] | [name] | [date]   | Open   |

## Next Steps
[One paragraph: what happens next, when the next touchpoint is,
and what must be true before that touchpoint]
```

### E. Internal Meeting Output

```
# Internal Meeting Summary
**Date:** [date]
**Meeting Type:** [Standup / Sprint Review / Planning / Strategy / 1-on-1 / Other]
**Attendees:** [names]

---

## Purpose
[One sentence: why this meeting was held]

## Key Decisions Made
- [Decision 1 — include rationale if discussed]
- [Decision 2]
(Omit section if no decisions were made)

## Discussion Highlights
[3-5 sentence narrative capturing the most important points]

## Action Items
| # | Action | Owner | Due Date | Status |
|---|--------|-------|----------|--------|
| 1 | [task] | [name] | [date]   | Open   |
| 2 | [task] | [name] | [date]   | Open   |

## Open Questions / Parking Lot
- [Unresolved question 1]
- [Unresolved question 2]
(Omit section if none)

## Next Meeting / Follow-Up
[When is the next check-in and what should be ready by then]
```

## Writing Rules

1. **Action items are non-negotiable.** Every action item must have an Owner. If the owner is unclear from the notes, flag it: `Owner: ⚠️ TBD — confirm with team`.
2. **Due dates are non-negotiable.** If no due date was stated, infer a reasonable one and mark it: `Due: ~Feb 14 (estimated)`.
3. **Use the client's language** in Sales meeting "Client Needs" bullets — do not rephrase into corporate jargon.
4. **The Unique Proposition Statement** must be exactly one sentence, written from the client's perspective, focusing on outcome not features.
5. **Omit empty sections** rather than writing "N/A" or "None discussed."
6. **Keep it scannable.** Executives should get value from a 30-second skim.
7. **If notes are sparse,** surface what you can and explicitly note gaps: `⚠️ Notes did not capture [X] — confirm with attendees.`

## MBAC rules (Counseling Session, Discovery Call, Workshop)

These are not optional. They come from the MBAC Context Document and the MBAC Global Instructions.

1. **Every summary ends with a scheduled next touch.** A summary with no next touch is not finished. No dead ends.
2. **Use the client's own words** for what they came in for. Never paraphrase the need into program jargon.
3. **The 24-hour rule.** A counseling session summary is logged to the client record within 24 hours of the session ending. Say so at the top of your output if the session is already older than that.
4. **PII stays out of the chat.** Financials, tax documents, ID documents, SSNs, home addresses, and dates of birth do not go into the summary or the conversation. If the notes contain them, flag it — `⚠️ Notes contain PII; log this to the client record in the connected store only` — and leave the detail out.
5. **You draft, a human sends and logs.** The counselor who was in the room approves the summary before it is logged. You were not there; they were.
6. **Flag, do not invent.** If a program rule, deadline, dollar amount, or referral name is not in the notes, mark it unverified rather than filling it in.
7. **Where it lands.** Counseling summaries and discovery notes go to the client record in the connected store; the Monday item just gets its status moved and its next-touch date set. Workshop debriefs go on the event item in the Workshops & Events board.