Summarizing & Condensing prompts

Quickly distills any article into five scannable takeaways; ideal for research triage or newsletter curation.

Read the following article and summarize it into exactly five concise bullet points. Each bullet should be one sentence and capture a distinct key idea. Do not repeat information across bullets.

Article:
[PASTE ARTICLE HERE]

How to use: Paste the full article text in place of [PASTE ARTICLE HERE]; adjust the number of bullets if needed.

Transforms raw meeting transcripts into a structured action-item list; perfect for follow-up emails after any meeting.

You are a professional meeting facilitator. Read the meeting transcript below and extract a clean, numbered list of action items. For each action item, include: (1) what needs to be done, (2) who is responsible (if mentioned), and (3) any stated deadline. If information is missing, write 'Not specified'.

Transcript:
[PASTE TRANSCRIPT HERE]

How to use: Paste the transcript and optionally specify a team name or meeting date in the prompt for context.

Produces a tight executive summary tailored to a specific audience; useful for briefing busy stakeholders.

Summarize the following document in a single, well-constructed paragraph of no more than [WORD_LIMIT] words. The summary should be written for [AUDIENCE, e.g. 'senior executives with no technical background'] and focus on the main conclusion, key findings, and any recommended next steps.

Document:
[PASTE DOCUMENT HERE]

How to use: Set [WORD_LIMIT] (e.g. 150) and describe your [AUDIENCE] clearly to shape the tone and vocabulary.

Generates a jargon-free TL;DR for academic papers; great for sharing research with non-specialist colleagues.

Read the research paper below and write a TL;DR (Too Long; Didn't Read) summary of 3–5 sentences. The summary must cover: the research question, the methodology in plain language, the main finding, and the practical implication. Avoid jargon.

Paper:
[PASTE PAPER HERE]

How to use: Works best when the full abstract and conclusion sections are included in the pasted text.

Breaks down dense legal language into plain-English sections; ideal for contracts, terms of service, or policy documents.

You are a plain-language legal editor. Read the legal document below and provide a summary written for a general audience with no legal training. Structure your output as follows:
- **What this document is**: one sentence
- **Key obligations**: bullet list
- **Key rights**: bullet list
- **Important dates or deadlines**: bullet list
- **Anything the reader should watch out for**: bullet list

Do not provide legal advice; note that professional review is recommended.

Document:
[PASTE LEGAL DOCUMENT HERE]

How to use: Paste any legal document and remind the final reader to seek professional counsel for binding decisions.

Produces three nested summaries of increasing depth; useful when different stakeholders need different levels of detail.

Summarize the document below at three levels of detail:
1. **One-liner** (max 25 words): the single most important point.
2. **Short summary** (3–5 sentences): the core argument, key evidence, and conclusion.
3. **Detailed summary** (one paragraph per major section): preserve important nuance and supporting details.

Label each level clearly.

Document:
[PASTE DOCUMENT HERE]

How to use: Share the one-liner with executives, the short summary with managers, and the detailed version with subject-matter experts.

Structures a podcast transcript into labeled topic segments with quotes; ideal for show notes or content repurposing.

Read the podcast transcript below and organize the content into topic segments. For each segment:
- **Topic heading** (concise label)
- **Time range** (if timestamps are present; otherwise write 'N/A')
- **2–3 sentence summary** of what was discussed
- **One memorable quote** from that segment (exact words from the transcript)

Transcript:
[PASTE TRANSCRIPT HERE]

How to use: If timestamps are missing, instruct the model to estimate order based on speaker transitions.

Converts a dense financial report into a board-ready briefing with a metrics table and discussion questions.

You are a financial analyst preparing a briefing for [AUDIENCE, e.g. 'board members who are not finance specialists']. Read the financial report below and produce a structured briefing with these sections:
1. **Overall performance snapshot** (2–3 sentences)
2. **Top 3 positive developments** (bullet list)
3. **Top 3 risks or concerns** (bullet list)
4. **Key metrics to watch** (table with Metric | Value | What it means)
5. **Recommended questions for management** (bullet list)

Avoid unexplained financial jargon.

Report:
[PASTE REPORT HERE]

How to use: Specify the audience's financial literacy level in [AUDIENCE] to calibrate the vocabulary appropriately.

Synthesizes unstructured customer feedback into labeled themes with sentiment; useful for product and UX teams.

Below is a collection of customer feedback responses. Read all responses and produce a thematic summary:
1. Identify the top [NUMBER, e.g. 5] recurring themes.
2. For each theme: write a theme label, a 2-sentence description, an approximate sense of how commonly it appeared (frequent / occasional / rare), and one representative verbatim quote.
3. Close with a 3-sentence overall sentiment summary.

Feedback responses:
[PASTE FEEDBACK HERE]

How to use: Adjust [NUMBER] based on the volume of feedback; more responses warrant more themes.

Reframes a report or policy document as an FAQ; great for onboarding materials or help-center content.

Read the document below and convert its key information into a Frequently Asked Questions (FAQ) format. Generate [NUMBER] question-and-answer pairs. Each question should be something a curious [AUDIENCE, e.g. 'new employee'] might genuinely ask, and each answer should be concise (2–4 sentences), accurate to the source, and written in plain language.

Document:
[PASTE DOCUMENT HERE]

How to use: Set [NUMBER] between 8 and 15 for most documents; increase for longer, denser source material.

Side-by-side comparison summary of two documents, surfacing agreements, differences, and unique insights.

You will receive two documents on the same topic. Read both carefully and produce a structured comparison summary:
1. **What they agree on**: bullet list of shared positions or findings.
2. **Where they differ**: table with columns — Topic | Document A's position | Document B's position.
3. **Unique insights in Document A only**: bullet list.
4. **Unique insights in Document B only**: bullet list.
5. **Overall synthesis** (2–3 sentences): what someone should take away from reading both.

Document A ([LABEL_A]):
[PASTE DOCUMENT A HERE]

Document B ([LABEL_B]):
[PASTE DOCUMENT B HERE]

How to use: Replace [LABEL_A] and [LABEL_B] with short identifiers like report titles or author names for readable output.

Forces a jargon-free summary with inline definitions; ideal for translating technical content to a general audience.

Summarize the following [DOCUMENT_TYPE, e.g. 'technical white paper'] in plain English for a reader who has no background in [FIELD, e.g. 'machine learning']. Your summary must:
- Be no longer than [WORD_LIMIT] words.
- Use zero domain-specific jargon; if a technical term is unavoidable, define it immediately in parentheses.
- Cover the problem being solved, the proposed solution, and the stated outcome.

Document:
[PASTE DOCUMENT HERE]

How to use: Be specific in [FIELD] and [DOCUMENT_TYPE] so the model knows which terms to flag as jargon.

Extracts and ranks insights by relevance to a stated goal; useful for strategy work or competitive research.

Read the document below. Identify the [NUMBER, e.g. 10] most valuable insights. Rank them from most to least significant based on their potential impact on [GOAL, e.g. 'improving customer retention']. Present as a numbered list where each entry includes: the insight (one sentence), why it matters for [GOAL] (one sentence), and the source section or quote that supports it.

Document:
[PASTE DOCUMENT HERE]

How to use: The more specific [GOAL] is, the more targeted and useful the ranked list will be.

Creates a sentiment-aware summary of multi-speaker transcripts; valuable for sales call reviews or conflict analysis.

Read the conversation transcript below. Produce a summary that:
1. Briefly describes the overall purpose and outcome of the conversation (2 sentences).
2. For each named speaker, provides a 2–3 sentence summary of their main points AND a one-word sentiment label (e.g. Positive, Skeptical, Frustrated, Neutral) with a one-sentence justification.
3. Highlights any moments of strong agreement or significant disagreement between speakers.
4. Lists any unresolved questions or tensions at the end of the conversation.

Transcript:
[PASTE TRANSCRIPT HERE]

How to use: Works best with transcripts where speakers are clearly labeled; ask the model to infer speaker names if not labeled.

Writes a formal IMRaD-structured abstract from a full paper; ideal for researchers preparing journal submissions.

Using the document below, write a structured abstract following the IMRaD format:
- **Introduction** (1–2 sentences): the research problem and motivation.
- **Methods** (2–3 sentences): study design, data sources, and analytical approach.
- **Results** (2–3 sentences): primary findings with key figures if mentioned.
- **Discussion** (1–2 sentences): interpretation and significance of the findings.
- **Conclusion** (1 sentence): the core takeaway and any future direction stated.

Target word count: [WORD_LIMIT, e.g. 250].

Document:
[PASTE PAPER HERE]

How to use: Adjust [WORD_LIMIT] to match the target journal's abstract requirements.

Synthesizes a literature review and surfaces research gaps; essential for academics designing new studies.

You are a research methodologist. Read the literature review below and produce:
1. **Core consensus** (bullet list): what most sources agree on.
2. **Contested claims** (bullet list): areas where sources disagree, with a note on the nature of the disagreement.
3. **Research gaps** (bullet list): topics that are under-explored or explicitly called out as needing further study.
4. **Methodological patterns** (2–3 sentences): what research methods dominate this field.
5. **Summary paragraph** (max 150 words): synthesizing all of the above for a reader unfamiliar with the field.

Literature review:
[PASTE TEXT HERE]

How to use: Include as many source excerpts as possible in the pasted text to improve gap detection accuracy.

Combines neutral summarization with critical claim-flagging; ideal for fact-checking or editorial review workflows.

Read the document below and produce a critical summary. Your output must include two sections:

**Section 1 – Summary**: A clear, neutral summary of the document's main arguments and conclusions (max [WORD_LIMIT] words).

**Section 2 – Unsupported or questionable claims**: A bullet list of any claims in the document that appear to lack cited evidence, seem exaggerated, or contradict well-established knowledge. For each, quote the exact claim and briefly explain the concern.

Document:
[PASTE DOCUMENT HERE]

How to use: Set a reasonable [WORD_LIMIT] for the summary; the claims list length will vary based on document quality.

Distills a long email chain into decisions, open items, and a next step; saves time in inbox triage.

Below is an email thread. Read the entire thread chronologically and produce:
1. **Thread purpose** (1 sentence): what the conversation is about.
2. **Key decisions made** (bullet list, with the name of the decision-maker if mentioned).
3. **Open items** (bullet list): questions asked but not yet answered, or tasks mentioned but not confirmed.
4. **Timeline of events** (if applicable): any dates or deadlines referenced.
5. **Recommended next step** (1 sentence): the single most logical action to move this forward.

Email thread:
[PASTE EMAIL THREAD HERE]

How to use: Paste the full thread with headers intact (From, Date, Subject) for better chronological accuracy.

Restructures dense prose into a scannable, web-friendly format with callouts; great for blog posts or internal wikis.

Reformat the following document into a highly skimmable summary designed for online reading. Use:
- **Bold headers** for each major section.
- Short paragraphs (max 3 sentences each).
- Bullet lists wherever items are enumerable.
- A highlighted **Key Takeaway** callout box (formatted as a blockquote) after each major section.
- A **Bottom Line** section at the end: the single most important thing to remember.

Document:
[PASTE DOCUMENT HERE]

How to use: Works well for converting reports or white papers into readable knowledge-base articles.

Translates formal policy documents into plain do/don't lists for operational staff; reduces compliance errors.

You are translating a formal policy document for [ROLE, e.g. 'front-line retail employees']. Read the policy below and write a summary that:
- Opens with a one-sentence statement of what this policy requires of [ROLE].
- Lists the top [NUMBER, e.g. 5] things [ROLE] must do (numbered, plain English).
- Lists the top [NUMBER] things [ROLE] must NOT do (numbered, plain English).
- Explains what happens if the policy is violated (if stated).
- Ends with a 'Who to contact' note (if names or roles are mentioned).

Use simple, direct language. Avoid legal or bureaucratic phrasing.

Policy document:
[PASTE POLICY HERE]

How to use: Specify [ROLE] precisely so the tone and examples are relevant to that job function.

Generates three tone-varied social captions from a single article; speeds up content repurposing for social teams.

Read the article below. Write three alternative social media caption summaries, each in a different tone:
1. **Professional/informative**: factual, neutral, suitable for [PLATFORM, e.g. 'LinkedIn'].
2. **Conversational/engaging**: approachable, uses a question or hook, suitable for general audiences.
3. **Punchy/attention-grabbing**: bold, short, designed to stop a scroll.

Each caption must be under [CHARACTER_LIMIT, e.g. 280] characters, accurately reflect the article, and include a call to action or relevant hashtags if appropriate.

Article:
[PASTE ARTICLE HERE]

How to use: Set [CHARACTER_LIMIT] to match the platform (e.g. 280 for X/Twitter, 2200 for Instagram).

Uses a visible chain-of-thought method to produce transparent, well-structured summaries; useful for verifying reasoning.

Summarize the document below using the following step-by-step process. Show your work at each step before producing the final summary.

Step 1 – Identify the main topic: State the central subject in one sentence.
Step 2 – List key sections: Name each major section or argument.
Step 3 – Extract the core claim per section: One sentence per section.
Step 4 – Identify the overall conclusion: What does the document ultimately argue or recommend?
Step 5 – Write the final summary: Synthesize steps 1–4 into a coherent paragraph of no more than [WORD_LIMIT] words.

Document:
[PASTE DOCUMENT HERE]

How to use: The intermediate steps help you audit the summary's logic; remove them in the final output if sharing externally.

Synthesizes multiple articles into a discourse map; ideal for literature scanning or competitive analysis.

Below are [NUMBER] articles on the topic of [TOPIC]. Read all of them and produce a cross-article synthesis:
1. **Shared themes** (bullet list): ideas that appear in multiple articles, with a note on how many mention each.
2. **Contrasting perspectives** (bullet list): where articles take different stances, and what the divide is.
3. **Emerging trends** (bullet list): new ideas or angles that appear in only the more recent articles.
4. **Synthesis paragraph** (max 200 words): a coherent overview of the current state of discourse on [TOPIC].

Articles:
[PASTE ALL ARTICLES HERE, separated by '---']

How to use: Separate each article with '---' and label them (Article 1, Article 2…) for cleaner attribution in the output.

Turns technical documentation into a clean one-pager for non-technical stakeholders; great for investor or executive decks.

You are a technical writer creating a one-pager for [AUDIENCE, e.g. 'investors with no engineering background']. Read the technical document below and produce a one-page summary (max [WORD_LIMIT, e.g. 400] words) structured as:
- **The Problem** (2–3 sentences)
- **The Solution** (2–3 sentences, no technical jargon)
- **How It Works** (3–5 bullet points, each one plain-English analogy or simple explanation)
- **Key Benefits** (bullet list)
- **Current Status / Next Steps** (2 sentences)

Avoid acronyms unless defined. Use analogies to familiar concepts where helpful.

Document:
[PASTE DOCUMENT HERE]

How to use: The more specific you are about [AUDIENCE], the better the analogies and vocabulary will be calibrated.

Scores and filters a document by relevance to a stated goal, then summarizes only the relevant portions.

You will read a document and evaluate how relevant it is to the following goal: [GOAL, e.g. 'understanding the competitive landscape for electric vehicle batteries in Europe'].

Produce:
1. **Relevance score**: rate the document's relevance to the goal on a scale of 1–10 and explain the score in 2 sentences.
2. **Relevant content** (bullet list): the specific sections, data points, or claims that directly support the goal.
3. **Irrelevant or off-topic content** (1 sentence): briefly characterize what can be ignored.
4. **Summary of relevant content** (max 150 words): a focused summary of only the parts that serve the goal.

Document:
[PASTE DOCUMENT HERE]

How to use: Use [GOAL] to define a precise research question so the relevance score and filtered summary are actionable.

Formats a report into a professional briefing memo with standard structure; ready to send to leadership.

Using the report below, write a formal briefing memo addressed to [RECIPIENT, e.g. 'the Director of Operations']. Follow standard memo format:

**TO**: [RECIPIENT]
**FROM**: [SENDER_NAME_OR_ROLE]
**DATE**: [DATE]
**RE**: Summary of [REPORT_TITLE]

**Purpose** (1 sentence): why this memo is being sent.
**Background** (2–3 sentences): essential context.
**Key Findings** (numbered list, max [NUMBER] items).
**Recommended Actions** (numbered list).
**Conclusion** (1–2 sentences): the bottom line.

Keep the total memo under [WORD_LIMIT, e.g. 500] words. Use formal, clear language.

Report:
[PASTE REPORT HERE]

How to use: Fill in all the header placeholders before using; they make the memo immediately ready to send.