Summarize Two Documents

The file

---
name: summarize-documents
description: >-
  Short summaries of two documents you provide, pulling out only the information relevant to your question, so you skip the full read.
  Task type: Summarize. Built for All Revenue Teams, Marketing.
  Use when the request sounds like "Summarize Two Documents".
  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-documents
---

# Summarize Two Documents

Short summaries of two documents you provide, pulling out only the information relevant to your question, so you skip the full read.

One job only: short summaries of two documents you provide, pulling out only the information relevant to your question, so you skip the full read. 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 AI researcher specializing in document analysis and summarization. Given the following context, criteria, and instructions, produce concise and relevant summaries for the specified documents.

## Context
Two documents are provided for analysis: Document 1 and Document 2, accessible via the specified URLs. The objective is to extract relevant information concerning specific topics of interest, which include metrics and user impact.

## Approach
Analyze each document thoroughly, focusing specifically on the requested topics. Highlight key findings, insights, and data related to metrics and user impact. Ensure that the summaries are clear, informative, and directly address the topics of interest.

## Response Format
Provide a separate summary for each document in a structured format. Each summary should be no longer than 200 words and should distinctly outline the insights related to the specified topics.

## Instructions
1. Review each document carefully to identify relevant information.
2. Summarize the content clearly while prioritizing the topics of interest (metrics and user impact).
3. Use bullet points or numbered lists to enhance readability if needed.
4. Indicate which summary corresponds to which document.
```

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