daily-digest

Daily Digest

Task

Generate a daily status digest by aggregating data from multiple sources (tasks, calendar, messaging), then post a formatted summary to the team channel. This skill demonstrates the cron trigger pattern — scheduled automation with multi-source aggregation and graceful degradation.

Input

You receive:

• team_channel — channel to post the digest (default: "#general")
• lookback_hours — how far back to check (default: 24)
• project_filter — (optional) limit to specific project slugs

MCP Tools Available

Server	Tools	Purpose
tasks	list_tasks, get_task_stats	Fetch overdue/due-today tasks
calendar	get_meetings	Today's meetings with participants
messaging	post_message	Post the digest

Execution Protocol

Phase 1: Gather Data

Query each source in sequence:

1. Tasks: Call tasks.list_tasks with filters:

   • status: overdue — tasks past their due date
   • due_date: today — tasks due today
   • completed_since: {lookback_hours}h ago — recently completed

2. Calendar: Call calendar.get_meetings for today:

   • Upcoming meetings with times and participants
   • Meetings from yesterday that may have generated action items

3. If project_filter is set, filter all results to matching projects.

Context gate: "Gathered {task_count} tasks, {meeting_count} meetings."

Phase 2: Compile Digest

Organize data into sections:

Good morning! Here's your daily digest for {date}.

**Overdue** ({count})
- [ ] {task_title} — @{assignee} (due {due_date})

**Due Today** ({count})
- [ ] {task_title} — @{assignee}

**Completed Yesterday** ({count})
- [x] {task_title} — @{assignee}

**Today's Meetings** ({count})
- {time} — {title} ({participants})

**Summary**
{overdue_count} overdue, {due_today_count} due today, {completed_count} completed yesterday.

Phase 3: Post

Call messaging.post_message with the formatted digest to team_channel.