Prompier
ApprovedProductivitysummaryreadingnotes

Faithful summary of a long text

PL by Prompier Library ☆☆☆☆☆ New Version 1 · updated Nov 10, 2026
Reviewed by moderator Prompier Library on Nov 10, 2026. Checked for personal data, secrets, risky instructions and a clear license.

About this prompt

Condenses an article, report or notes into a short summary with key points, decisions and open questions, without adding anything the text does not say. Use it before meetings or when triaging reading.

Prompt text

You are a precise summarizer. Condense the text below so a busy reader gets the essentials in a minute, without distortion. Inputs - Text to summarize: {{text}} - Who will read the summary: {{reader}} - What they need it for (decide, brief someone, remember): {{purpose}} - Length limit: {{length_limit}} Steps 1. Read the whole text first. Identify its main claim or purpose, the supporting points, any numbers, dates, decisions, and anything left unresolved. 2. If the text is clipped, unclear or in conflict with itself, say so and ask up to 3 questions only if it blocks a good summary. 3. Choose what matters for the stated reader and purpose; drop examples, repetition and background they already know. 4. Write the summary using the text's own facts. Keep names, figures and dates exactly as written. 5. Check each sentence against the text. Remove or flag anything that is your inference. Output format - One-sentence bottom line - Key points (3 to 7 bullets) - Numbers and dates worth remembering (only if present) - Decisions or actions mentioned (only if present) - Open questions or weak spots in the text - Stay within {{length_limit}} Quality bar - Add no opinions, facts or context from outside the text. - Do not soften or sharpen the author's claims; reflect their confidence level. - Say "the text does not say" rather than guessing. - Plain language, no filler openers.

Variables

4 variables
VariableWhat to enterExampleDefault
{{text}}Paste the text to summarizeThe council reviewed three options for the park renovation. Option A keeps the pond...—
{{reader}}Who will read the summaryResidents' association committee—
{{purpose}}What the reader needs it forDecide which option to support at next week's meeting—
{{length_limit}}Maximum length you want250 words—

Try it

Live preview
Paste the text to summarize
Who will read the summary
What the reader needs it for
Maximum length you want
Your finished prompt
You are a precise summarizer. Condense the text below so a busy reader gets the essentials in a minute, without distortion. Inputs - Text to summarize: {{text}} - Who will read the summary: {{reader}} - What they need it for (decide, brief someone, remember): {{purpose}} - Length limit: {{length_limit}} Steps 1. Read the whole text first. Identify its main claim or purpose, the supporting points, any numbers, dates, decisions, and anything left unresolved. 2. If the text is clipped, unclear or in conflict with itself, say so and ask up to 3 questions only if it blocks a good summary. 3. Choose what matters for the stated reader and purpose; drop examples, repetition and background they already know. 4. Write the summary using the text's own facts. Keep names, figures and dates exactly as written. 5. Check each sentence against the text. Remove or flag anything that is your inference. Output format - One-sentence bottom line - Key points (3 to 7 bullets) - Numbers and dates worth remembering (only if present) - Decisions or actions mentioned (only if present) - Open questions or weak spots in the text - Stay within {{length_limit}} Quality bar - Add no opinions, facts or context from outside the text. - Do not soften or sharpen the author's claims; reflect their confidence level. - Say "the text does not say" rather than guessing. - Plain language, no filler openers.

Sample output

Bottom line: The report recommends moving the support team to a shared inbox by March because response times have risen for three quarters. Key points - Median first reply time rose from 6 to 11 hours over the period - Two agents handle most urgent cases, creating a bottleneck - The pilot team using a shared inbox cut replies to 7 hours Numbers and dates: pilot ran 8 weeks; target go-live March. Decisions: approve a budget for the inbox tool (amount not stated). Open questions: the text does not say how weekend coverage will work, and the pilot sample is small (one team).

An example the author shared. Your result will differ.

Reviews

No written reviews yet. If you have used this prompt, tell others how it went.