prompt library

for use with microsoft copilot + export to a loop page

Generic Daily Summary Prompt (Shareable + Customizable)

You are my enterprise productivity assistant. Generate a Loop-ready daily summary using my enterprise workspace data FIRST (email, chat, calendar, documents) and supplement with credible web news LAST. Follow these rules exactly.

OUTPUT FORMAT (Markdown for Loop)

• H1: Today’s date in long form (e.g., October 16, 2025)
• Each section is an H2
• Use tables (no HTML) where specified
• Include working links for sources (emails, chats, files, news)
• Tone: concise, executive-level

SECTIONS TO PRODUCE (IN ORDER)

1. Summary of {Last Workday}

• Automatically determine “last workday.”
• Provide 2–4 crisp sentences summarizing my focus across meetings, chats, and email.
• Do not split by source.
• Write as an update to my leader.

2. Last 7 Days Overview

Create a 3-column, 3-row table:

| Highlights | Challenges | Next Steps |

• Base bullets on activity across the last 5 business days.
• Be specific (projects, decisions, owners, blockers) but brief.
• Pull from chat threads, meeting notes/transcripts, and email themes.

3. Product Notes + Tasks

Provide an empty table:

| Tasks | Priority | Kanban | Product | Notes |

• Priority: Loop “Label” dropdown using a Priority label group
• Kanban: Loop “Label” dropdown using a Kanban label group
• Product: Loop “Label” dropdown using a custom product/category label group

Issue-Tracking Notifications to Follow Up (≤10 items; last 7 days)

• Extract from issue-tracking email notifications (using organization-specific subject prefixes).
• One bullet per issue: KEY — short title.
• Exclude items marked irrelevant by the user.

4. Daily Agenda

Populate from today’s calendar:

| Time | Meeting | Resources / Docs |

• Include links to relevant files, notes, and project pages.
• Do not list full invitees.

5. Quick Actions

Provide 3–4 links I likely need today, such as:

• Issue-tracking board
• Primary chat channel from yesterday
• Incident / change dashboard
• Recently referenced reports or dashboards

6. After-Hours Catch-Up

Scan messages from yesterday 5:30 PM to today 2:00 AM.

Provide three lists (1–3 bullets each):

Decisions — what / owner / impact

Asks for Me — what’s needed and by when

Heads-Up / Risks — context + impact

Threads to read first (max 3):

• Include channel/chat name, thread title, and link.

7. Important News

Industry (based on the user’s field)

• 2–3 recent articles (within 7 days)
• 1-sentence takeaway per article + link

Company

• Current stock price (real-time or last close)
• 1–2 notable updates with links

Sector (industry-specific)

• 1–2 noteworthy items with links

8. On This Day in {Industry/Company} History

• Provide one concise, verifiable event.
• Include a reputable citation link.

DATA & METHOD REQUIREMENTS

• Use enterprise workspace signals first:
  • Email (last 7 days)
  • Chat conversations
  • Meeting transcripts and notes
  • Calendar data
• Issue-tracking follow-ups: use relevant email notifications; cap at 10.
• After-hours scan: prioritize @mentions and critical keywords.
• For internal references, include working links.
• For web news, cite authoritative sources.

STYLE GUARDRAILS

• Be accurate, concise, specific.
• No filler.
• Max 20 words per bullet.
• Keep empty sections with “No updates found.”
• Do not list full meeting invitees.
• Do not expose private information outside the organization.

END OF INSTRUCTIONS — now generate today’s summary.

for use with microsoft copilot + export to a loop page

Summarize all important communications I received while out of office over the last {X} business days.

Output Requirements

1. High-Priority Summary
   • Start with a bulleted list of high-priority items from {Manager Name / Leadership Team}.
   • Highlight decisions, requests, blockers, or time-sensitive updates.
2. Communication Breakdown Provide separate tables for each category below:
   • Chat messages
   • Emails
   • Issue-tracking notifications
   • Files or documents shared
   • Meeting recaps or recordings
3. Prioritization Rules
   • Prioritize items that:
     • Have due dates before {Timeframe / Key Milestone}
     • Are marked urgent, blocking, or action required
     • Reference active projects or commitments owned by me
4. Resource Reference List
   • Include a final section with a reference list:
     • Direct links to messages, files, tickets, and meeting notes
     • Group links by category where possible

Style Guidelines

Do not expose sensitive or private information

Be concise and scannable

Use clear titles and tables

Exclude low-signal or FYI-only items