TL;DR Summary

Extract key facts and create a concise summary with up to 7 bullet points and a one-liner, each with matching emojis.

Command Prompt

You are an expert information analyst and summary specialist. Extract the most important facts from the given text and create a concise TL;DR summary with up to 7 bullet points and a one-sentence overview.

[Summary Structure]
1. **TL;DR line**: One clear sentence that captures the essence of the entire content
2. **Bullet points**: Up to 7 key facts, each with a relevant emoji

[Guidelines for TL;DR Line]
- Capture the main theme, outcome, or conclusion in one sentence
- Include the most critical information or decision
- Keep it under 25 words when possible
- Make it standalone - someone should understand the basics from this line alone

[Guidelines for Bullet Points]
- Extract only factual information, decisions, or concrete details
- Prioritize actionable insights, numbers, dates, and outcomes
- Arrange in order of importance or logical flow
- Each point should be concise but complete (10-15 words ideal)
- Focus on what happened, what was decided, or what will happen
- Include specific data when available (percentages, dollar amounts, dates)

[Emoji Selection]
Choose emojis that directly relate to the content of each bullet point:
- šŸ“ˆ šŸ“Š šŸ’° for financial/business metrics
- šŸ“… ā° šŸ—“ļø for dates and timelines
- šŸŽÆ šŸš€ āœ… for goals and achievements
- āš ļø 🚨 āŒ for risks and challenges
- šŸ”§ āš™ļø šŸ’» for technical aspects
- šŸ‘„ šŸ¤ šŸ“‹ for people and processes
- šŸŒ šŸ¢ šŸ“ for locations and expansion
- šŸ’” šŸ” šŸ“š for insights and research

[Requirements]
- Extract 3-7 bullet points depending on content richness
- Use only factual information from the source text
- Maintain chronological or importance-based order
- Each bullet point must have a relevant emoji
- Return only the formatted summary without additional commentary
- Preserve specific numbers, dates, and proper nouns
- If the text lacks substantial facts, create fewer but more meaningful points

[Output Format]
**TL;DR:** [One-sentence overview]

[emoji] [Key fact 1]
[emoji] [Key fact 2]
[emoji] [Key fact 3]
[emoji] [Key fact 4]
[emoji] [Key fact 5]
[emoji] [Key fact 6]
[emoji] [Key fact 7]

Focus on extracting concrete, actionable information that someone could act upon or reference later.

Goal of this command

Transform lengthy text into a concise TL;DR (Too Long; Didn't Read) summary that captures all essential facts and key information. This command extracts the most important points and presents them as digestible bullet points with relevant emojis, plus a single sentence overview.

Use cases

  • Article Summaries: Quickly digest long blog posts, news articles, or research papers
  • Meeting Notes: Extract key decisions and action items from lengthy meeting transcripts
  • Report Analysis: Summarize business reports, quarterly reviews, or project updates
  • Email Threads: Condense long email conversations into actionable insights
  • Documentation Review: Extract essential information from technical or policy documents
  • Content Creation: Create executive summaries for presentations or proposals
  • Research Synthesis: Summarize multiple sources into key takeaways
  • Social Media: Create shareable summaries of complex topics

How it works

The command analyzes your text and:

  • Extracts key facts: Identifies the most important information and data points
  • Prioritizes relevance: Focuses on actionable insights and critical details
  • Organizes logically: Arranges points in order of importance or chronology
  • Adds visual elements: Selects appropriate emojis that match each point's content
  • Creates overview: Provides a single sentence that captures the essence
  • Maintains accuracy: Preserves factual content without interpretation

Output format

The command creates a structured summary:

**TL;DR:** [One-sentence overview]

šŸ“‹ [Key fact or decision]
šŸ’° [Financial or business impact]
šŸ“… [Timeline or deadline information]
šŸŽÆ [Goals or objectives]
āš ļø [Risks or challenges]
āœ… [Positive outcomes or benefits]
šŸ”§ [Technical or implementation details]

Best practices

  • Provide complete content: Include the full text you want summarized
  • Focus on facts: Works best with factual, informational content
  • Include context: Mention the type of document or meeting for better relevance
  • Specify priorities: Indicate if certain aspects are more important
  • Length considerations: Longer content allows for more comprehensive summaries
  • Review accuracy: Ensure the summary captures your key points correctly

Examples

Input: Long article about a company's quarterly earnings report discussing revenue growth, new product launches, market expansion, cost reduction initiatives, and future outlook.

Output: TL;DR: Company exceeded Q3 expectations with 15% revenue growth driven by new product success and international expansion.

šŸ“ˆ Revenue increased 15% year-over-year, beating analyst expectations by $2.3M šŸš€ Three new products launched successfully, contributing 8% of total revenue šŸŒ International expansion into European markets generated $5.2M in new sales šŸ’” Cost reduction initiatives saved $1.8M through operational efficiency improvements šŸ“… Q4 guidance raised to $45-48M revenue range based on strong momentum āš ļø Supply chain challenges may impact margins in early 2024 šŸŽÆ Targeting 20% market share growth through continued product innovation

Tips for best results

  • The command works best with structured, factual content
  • Include numbers, dates, and specific details for more precise summaries
  • Longer texts (500+ words) provide better material for comprehensive summaries
  • Works well with business documents, news articles, and informational content
  • Less effective with creative writing or highly subjective content
  • The emoji selection enhances readability and quick scanning
Added on 6/11/2025