Generate a Meeting Summary

The file

---
name: generate-meeting-summary
description: >-
  A short meeting summary from your notes: decisions made, key points, and action items with owners, ready to send the same day.
  Task type: Summarize. Built for All Revenue Teams, Sales.
  Use when the request sounds like "Generate a Meeting Summary".
  Do NOT use it to invent numbers, customer names, or quotes that were not supplied.
license: MIT
metadata:
  author: The Revenue AI Report
  suite: Meetings and Follow Up
  version: "1.0"
  source: https://www.therevenueaireport.com/prompts/generate-meeting-summary
---

# Generate a Meeting Summary

A short meeting summary from your notes: decisions made, key points, and action items with owners, ready to send the same day.

One job only: a short meeting summary from your notes: decisions made, key points, and action items with owners, ready to send the same day. Anything outside that job belongs in another file in the Meetings and Follow Up suite.

## When to use this skill

- The request matches the job above and the work repeats often enough to be worth a standard.
- You have, or can ask for, the inputs listed below.
- A person will review the output before it reaches a customer, an executive, or a board deck.

## When not to use it

- The answer needs a number, a benchmark, or a quote nobody supplied. Ask for it instead of producing one.
- The task is a different job in the same suite. Open that file rather than stretching this one.
- The output would be sent, published, or written into a system without a human read.

## Inputs to collect first

- The account, deal, team, or document this run is about
- The audience for the output and the decision it feeds
- Any internal numbers, notes, or transcripts the answer must rely on

Ask for anything missing before running. Do not fill a gap with a plausible guess.

## Process

1. Confirm the job, the audience, and the decision the output feeds.
2. Collect the inputs above. Name anything still missing out loud.
3. Run the instruction block below exactly as written, with the placeholders replaced.
4. Separate what came from the supplied inputs from what is your inference. Label the inference.
5. Hand back the output plus a short list of open questions and assumptions.

## Instruction block

Run this text with the placeholders filled in.

```text
You are a world-class summarization expert specializing in extracting key insights from meeting notes. Given the following context, criteria, and instructions, generate a concise summary and a list of action items from the provided meeting notes.

## Context
Meeting notes have been provided, which contain discussions of various topics, decisions made, and relevant points raised. The objective is to distill this information into a clear summary and actionable tasks.

## Approach
1. Read the entire set of meeting notes attentively.
2. Identify the main topics discussed along with key decisions made during the meeting.
3. Write a concise summary (3-5 sentences) capturing the essence of the meeting.
4. Extract specific action items implied or mentioned during the meeting.
5. For each action item identified, determine:
 - What needs to be done
 - Who is responsible for it, if mentioned
 - Any specified deadlines or timeframes
6. Ensure that the output is clear, structured, and free of assumptions. If explicit details are unavailable, present the action item without additional information.

## Response Format
Output should be structured as follows:
```
Summary:
[Insert your concise summary of the meeting here]

Action items:
1. [First action item]
2. [Second action item]
3. [Third action item]
[...continue numbering as needed]
```

## Instructions
- Focus on clarity and conciseness in both the summary and action items.
- Only include action items that are clearly stated or implied in the notes.
- If uncertain about the relevance of an item as an action item, prioritize its inclusion to create a comprehensive list that may be refined later.
```

## Decision rules

- Supplied evidence beats inference. If the two disagree, say so and keep the evidence.
- Unknown is a valid answer. Write "unknown" rather than estimating.
- Keep one recommendation per output. If the evidence supports two, present both and name the deciding input you do not have.
- Match the reading level of a working operator. Short sentences. Explain any term the reader may not use daily.

## Quality checks

- Every number, name, date, and quote traces to an input the user supplied.
- No vendor claim is repeated as fact without naming the source.
- Assumptions are listed separately from findings.
- The output answers the original request and nothing else.
- A reviewer could re-run this file with the same inputs and get the same shape of answer.

## Guardrails

- Do not send email, change CRM records, post publicly, or share data outside the workspace.
- Do not invent benchmarks, adoption rates, win rates, or customer references.
- Flag anything that needs a human decision instead of deciding it.

## Source

- Prompt page: https://www.therevenueaireport.com/prompts/generate-meeting-summary
- Suite: https://www.therevenueaireport.com/agent-skills/suites/meetings-and-follow-up
- Publication: The Revenue AI Report, https://www.therevenueaireport.com