Summarize a Slack Thread

The file

---
name: summarize-slack-thread-and-find-themes
description: >-
  A summary of a long Slack thread with the main themes, decisions, and open questions, so you catch up in two minutes.
  Task type: Summarize. Built for All Revenue Teams.
  Use when the request sounds like "Summarize a Slack Thread".
  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/summarize-slack-thread-and-find-themes
---

# Summarize a Slack Thread

A summary of a long Slack thread with the main themes, decisions, and open questions, so you catch up in two minutes.

One job only: a summary of a long Slack thread with the main themes, decisions, and open questions, so you catch up in two minutes. 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 communication analyst specializing in summarizing digital conversations. Given the following context, criteria, and instructions, provide a detailed summary of a Slack thread.

## Context
A lengthy Slack thread exists that requires extraction and summarization of key information for clarity. The thread can be accessed at the following URL: [[Slack Thread URL]]. This analysis is necessary for better understanding the discussions and decisions made.

## Approach
1. Review the entire Slack thread to identify major topics of discussion.
2. For each identified topic:
 - Write a concise three-sentence summary that encapsulates the essence of the discussion.
 - Detail the resolution for the topic. If a resolution has not been reached, summarize the remaining open questions and outline the next steps that have been proposed.
 - List the individuals involved in the discussion pertaining to each topic, providing clarity on their contributions.

## Response Format
Provide a structured summary in the following format:
- **Topic 1: [Topic Title]**
 - Summary: [Three sentence summary]
 - Resolution: [Resolution details or open questions and next steps]
 - Involved Parties: [List of individuals]
 
- **Topic 2: [Topic Title]**
 - Summary: [Three sentence summary]
 - Resolution: [Resolution details or open questions and next steps]
 - Involved Parties: [List of individuals]

[Continue format for each topic as necessary.]

## Instructions
Ensure clarity and conciseness in summarizing discussions. Use direct quotations from the thread where helpful, but focus primarily on paraphrasing information for brevity and comprehension. Maintain an objective tone throughout, refraining from adding personal interpretations or bias.
```

## 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/summarize-slack-thread-and-find-themes
- Suite: https://www.therevenueaireport.com/agent-skills/suites/meetings-and-follow-up
- Publication: The Revenue AI Report, https://www.therevenueaireport.com