Short-form Summary Prompts: Compress Without Losing Truth

12 prompt templates to summarize an article, paper, video, or thread to 100 / 250 / 500 words — without flattening nuance.

Summaries usually lose the one detail that makes the original useful. A good summary prompt names the audience, the keep-list (what must survive), and the drop-list (what’s safe to lose).

Who this is for

Newsletter writers, content marketers compressing whitepapers, executives reading research, students extracting essence from papers.

When not to use these prompts

Don’t use these for legal / medical / safety content where every word matters. Don’t use them to make false-balance summaries.

Prompt anatomy / structure formula

Every summary prompt should carry six elements:

  • Audience: one specific reader.
  • Goal: one outcome — read / click / agree / share.
  • Voice: 2-3 anchor adjectives.
  • Constraints: word count, banned phrases, must-include facts.
  • Format: paragraph, bulleted, headed, table.
  • Examples: 1-2 tone samples — best lever for matching voice.

Best for

  • Article → 250-word brief
  • Paper → 1-paragraph layperson summary
  • Long talk → tweet thread
  • Internal email → executive TL;DR
  • PDF / report → bullet brief

12 copy-ready prompt templates

1. Length-bound summary

Summarise this in exactly `{words}` words. Audience: `{audience}`. Must include: (a) main claim, (b) one supporting fact, (c) one nuance. Drop: history, methodology, hedges. Output count must match the target.

Variables to swap: words, audience

2. Paper → layperson

This is a research paper. Summarise in 150 words for a non-specialist: (1) Question asked, (2) What they did, (3) What they found, (4) One caveat, (5) Why anyone should care. No "the authors argue…" — use direct claims.

3. Talk → tweet thread

Convert this 45-min talk into a 8-tweet thread. Tweet 1: hook. Tweets 2-6: core arguments, one per tweet. Tweet 7: counter-point or caveat. Tweet 8: where to watch / read more. Each ≤ 280 chars.

4. Email → executive TL;DR

Above this 1000-word email, add a 3-line TL;DR: (1) Decision needed / FYI, (2) Recommendation if any, (3) Deadline. Keep the original body below intact.

5. Report → bullet brief

Summarise this 30-page report as: (1) 5 bullet findings, (2) 3 bullet recommendations, (3) 1 bullet of "what surprised us". Each bullet ≤ 25 words. Drop methodology unless it changes interpretation.

6. Multi-source summary

Read these 3 sources on the same topic. Produce a 200-word summary that: (a) names points of agreement, (b) names points of disagreement, (c) flags where sources contradict, (d) names the gap none of them cover.

7. Skeptic’s summary

Summarise this piece as a skeptical reader would. Compress to 150 words, leading with the strongest counter-evidence. The author would not love this summary — that's the point.

8. Comparison summary

Summarise A and B in parallel: 100 words each, same structure (who, claim, evidence, caveat). Output side by side. Highlight where their conclusions diverge.

9. Voice-preserving summary

Summarise this in 300 words while preserving the author's voice. Sample voice line: `{voiceSample}`. Don't flatten to neutral encyclopedia tone.

Variables to swap: voiceSample

10. Headline + one-line summary

Write 5 headlines (≤ 10 words each) and 5 one-line summaries (≤ 30 words) for this piece. Variety: outcome, problem, contrast, surprise, instruction. No clickbait.

11. Truth-preservation check

Audit this summary against the source. Flag: (1) Claims in summary not in source, (2) Important caveats dropped, (3) Hedges removed where they mattered, (4) Numbers changed. Output a list of fidelity issues.

12. Audience-shifted summary

I have a summary for engineers. Re-summarise for: (a) product managers, (b) executives, (c) end users. Each: 100 words. Keep the truth identical; shift which facts get emphasised.

Common mistakes

  • Vague audience — output reads generic.
  • No tone anchor — every variant comes back same flavour.
  • No constraints — word count, banned phrases, length cap.
  • Skipping examples — examples are the strongest signal for voice.
  • Trusting first draft — AI lands on safe middle.
  • Overusing AI clichés (“In today’s fast-paced…”).
  • No fact-check pass — AI is confidently wrong sometimes.

How to push results further

  • Give 1-2 tone examples; “be friendly” is noise.
  • Constrain ruthlessly.
  • Read aloud before publishing.
  • Cut adverbs / adjectives that don’t carry weight.
  • AI for drafts 1-2, human edit for 3 — and 3 is what ships.
  • Anchor in a real person from your audience.
  • Test the headline standalone.

Practical depth notes

Use these prompts as starting points, not final answers. For Short-form Summary Prompts: Compress Without Losing Truth, the useful extra work is to replace every generic placeholder with a real constraint: audience, channel, length, brand voice, examples to imitate, and examples to avoid. Run at least two versions with different constraints, then compare the outputs side by side instead of accepting the first polished response.

A good result should pass three checks: it is specific enough that another person could reuse it, it avoids vague praise or filler, and it gives you an editable artifact rather than a broad suggestion. If the output feels generic, add one concrete reference, one forbidden pattern, and one measurable success criterion before rerunning the prompt. Before saving a prompt as reusable, test it on one realistic input and one edge case. The realistic input proves the template can produce the normal deliverable; the edge case shows whether it handles messy constraints, missing context, or an unusual audience. Keep the better output, but also keep the failed version with a note on what was missing. That small failure log is what turns a prompt collection from a list of nice sentences into a practical working library. One final check: compare the finished result against the original goal in a single sentence. If that sentence is hard to write, the output is probably polished but unfocused. Tighten the goal, remove decorative language, and rerun only the weak section instead of regenerating the entire piece.

FAQ

  • How long should this piece be?: Match the channel — shorter where attention is shorter.
  • Can AI do the whole draft?: AI for first two passes, human for the third.
  • How often refresh?: When audience or claims change, or quarterly for evergreen content.
  • Should I publish without an edit pass?: No. AI is confident, not always correct.
  • Single voice or per-channel?: One brand voice; channels shift tone axes within voice.
  • Repurpose this prompt for other content types?: Yes — swap audience, goal, voice. Structure is reusable.

Tags: #Prompt #Writing #Summary