Summarize Anything

A summary is only useful if you can trust it — which means it can't quietly drop the caveat that changes everything or invent a takeaway that wasn't there. This compresses hard while staying faithful: the one-line gist for the busy, the key points for the skimmer, and — for threads and meetings — the decisions and who-owes-what, so a summary becomes something you can act on, not just a shorter read.

What This Skill Produces

• TL;DR — one line, the single most important thing
• Key points — the 3–7 that carry the meaning, as scannable bullets
• Decisions & action items — for threads/meetings: what was decided, who owns what, by when
• Open questions / caveats — what's unresolved or conditional (kept, not smoothed away)

Required Inputs

Ask for these if not provided:

• The source — paste the text (article, thread, doc, transcript)
• What you need from it — just the gist, or the decisions, or "should I read the whole thing?"
• Length — one-liner, a paragraph, or the fuller structured version

Framework: Compress Without Distorting