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
- Faithful first. Every point traces to the source; nothing is added, sharpened, or invented.
- Lead with the answer. The TL;DR is the conclusion, not "this document discusses…".
- Keep the load-bearing caveat. The "but only if…" is often the whole point — never drop it for brevity.
- Separate fact from opinion. Note when a "point" is the author's claim vs. established fact.
- Make threads actionable. Who decided what, who's on the hook, what's still open.
Output Format
TL;DR
One sentence.
Key points
Decisions & actions (threads/meetings)
| Decision / action |
Owner |
By |
Open / caveats
Quality Checks
Anti-Patterns
- Inventing a takeaway that sounds good but isn't in the source.
- Dropping the caveat that flips the meaning, in the name of brevity.
- "This article discusses…" throat-clearing instead of the actual point.
- Presenting opinion as fact by stripping the hedges the author used.
Example Trigger Phrases
- "TL;DR this article: [paste]"
- "Summarize this email thread and tell me what I need to do."
- "Give me the key takeaways from this transcript."
- "What's the gist of this doc — is it worth reading fully?"
- "Pull the decisions and action items out of these meeting notes."
1---2name: summarize-anything-23description: "Turn a long article, email thread, document, or transcript into a tight summary you can act on — the gist, the key points, and what it means for you. Use when asked for a TL;DR, to summarize this, give me the gist, or the key takeaways. Produces a one-line TL;DR, the key points as scannable bullets, any decisions/action items with owners, and open questions — faithful to the source, with nothing invented and important caveats kept."4homepage: https://mohitagw15856.github.io/pm-claude-skills/skill/summarize-anything.html5metadata:6 source: https://skillmd.com/skills/mohitagw15856/summarize-anything-27 openclaw:8 emoji: 📨9---1011# Summarize Anything1213A 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.1415## What This Skill Produces1617- **TL;DR** — one line, the single most important thing18- **Key points** — the 3–7 that carry the meaning, as scannable bullets19- **Decisions & action items** — for threads/meetings: what was decided, who owns what, by when20- **Open questions / caveats** — what's unresolved or conditional (kept, not smoothed away)2122## Required Inputs2324Ask for these if not provided:25- **The source** — paste the text (article, thread, doc, transcript)26- **What you need from it** — just the gist, or the decisions, or "should I read the whole thing?"27- **Length** — one-liner, a paragraph, or the fuller structured version2829## Framework: Compress Without Distorting30311. **Faithful first.** Every point traces to the source; nothing is added, sharpened, or invented.322. **Lead with the answer.** The TL;DR is the conclusion, not "this document discusses…".333. **Keep the load-bearing caveat.** The "but only if…" is often the whole point — never drop it for brevity.344. **Separate fact from opinion.** Note when a "point" is the author's claim vs. established fact.355. **Make threads actionable.** Who decided what, who's on the hook, what's still open.3637## Output Format3839### TL;DR40> One sentence.4142### Key points43- …4445### Decisions & actions *(threads/meetings)*46| Decision / action | Owner | By |47|---|---|---|4849### Open / caveats50- …5152## Quality Checks53- [ ] Every point is supported by the source — nothing invented or overstated54- [ ] The TL;DR is the actual conclusion, not a topic label55- [ ] Load-bearing caveats/conditions are preserved56- [ ] For threads/meetings, decisions and owners are pulled out57- [ ] The author's claims are distinguished from established facts where it matters5859## Anti-Patterns60- **Inventing a takeaway** that sounds good but isn't in the source.61- **Dropping the caveat** that flips the meaning, in the name of brevity.62- **"This article discusses…"** throat-clearing instead of the actual point.63- **Presenting opinion as fact** by stripping the hedges the author used.6465## Example Trigger Phrases66- "TL;DR this article: [paste]"67- "Summarize this email thread and tell me what I need to do."68- "Give me the key takeaways from this transcript."69- "What's the gist of this doc — is it worth reading fully?"70- "Pull the decisions and action items out of these meeting notes."