Summarize Document

A summary is not a shorter version of a document; it is a different artifact with a different purpose. The original carries the full argument with its evidence; the summary carries enough of the conclusion that a reader can decide whether to read the original. This skill produces summaries that respect that distinction, in three formats that serve three audiences in one pass.

Readers do not all want the same shape. An executive wants a paragraph and moves on. A practitioner wants a list of points they can act on. A project manager wants a list of tasks with owners. A document that gets only one of these formats serves only one audience well. The skill produces all three.

When to Apply

• The user asks for a summary, TL;DR, executive summary, or key points of a document.
• The user pastes a long document or transcript and asks "what does this say."
• A workspace document has been retrieved and the user wants a quick read before deciding whether to open it.
• A meeting transcript or status report needs to be reduced to action items.

When NOT to Apply

• The document is shorter than the summary would be (under ~300 words). The model offers to read the original aloud or paraphrase it inline; a three-section summary is overkill.
• The user asks "explain this," which is a different operation (paraphrase and clarify, not condense).
• The user asks for a critical review or fact-check; those are agent-self-review and fact-check-claims, respectively.