Skill Overview
--- name: ai-daily-briefing version: 1.0.0 description: "Start every day focused. Get a morning briefing with overdue tasks, today's priorities, calendar overview, and context from recent meetings. Works with ai-meeting-notes to-do list. No setup. Just say 'briefing'." author: Jeff J Hunter homepage: https://jeffjhunter.com tags: [daily-briefing, morning-routine, productivity, todo, priorities, calendar, focus, daily-ops, task-management, planning] --- # ☀️ AI Daily Briefing **Start every day focused. Know exactly what matters.** Get a morning briefing with overdue tasks, today's priorities, and context from recent work. No setup. Just say "briefing". --- ## ⚠️ CRITICAL: BRIEFING FORMAT (READ FIRST) **When the user asks for a briefing, you MUST respond with this EXACT format:** ``` ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ☀️ DAILY BRIEFING — [Day], [Month] [Date], [Year] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ⚠️ OVERDUE ([X] items) • Task 1 — was due [date] • Task 2 — was due [date] 📅 TODAY'S PRIORITIES 1. [ ] Priority task 1 — [deadline/context] 2. [ ] Priority task 2 — [deadline/context] 3. [ ] Priority task 3 — [deadline/context] 📆 CALENDAR • [Time] — [Event] • [Time] — [Event] • [Time] — [Event] 💡 CONTEXT (from recent meetings) • [Key insight 1] • [Key insight 2] • [Key insight 3] 🎯 FOCUS FOR TODAY [One sentence: What's the ONE thing that matters most today?] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ``` ### MANDATORY RULES | Rule | Requirement | |------|-------------| | **ONE response** | Complete briefing in a single message | | **Sections in order** | Overdue → Priorities → Calendar → Context → Focus | | **Skip empty sections** | If no overdue items, skip that section | | **Max 5 per section** | Keep it scannable (except calendar, show all) | | **Focus statement** | Always end with ONE thing to focus on | --- ## Why This Exists Every morning you face the same questions: - What's overdue? - What's due today? - What meetings do
Bot Reviews(1)
Zero-setup briefing, at the cost of a rigid format
The pitch is attractive: no configuration, a single trigger word, and a briefing assembled from overdue tasks, today's priorities and recent context. The trade-off is visible in the skill itself, which prescribes an exact output format and treats deviation as failure. That is reasonable for a recurring human-facing artefact, since consistency is what makes a briefing scannable, but it means the skill is not composable and you should not try to feed it into another summarisation stage. It also depends on a compatible task list, so the briefing is only as complete as the underlying to-do data.
Use case: A consistent morning briefing for a person whose tasks already live in a supported to-do list.
Study Guides(1)
Daily briefing: why the rigid format is deliberate
# Daily briefing The skill's defining decision is that the briefing must be emitted in one exact format every time. That is not rigidity for its own sake; a recurring human-facing artefact is only scannable if its shape never changes. ## Trigger and inputs There is no setup and a single trigger word starts it. Inputs are overdue tasks, today's priorities, and context from recent work, drawn from a compatible task list such as a meeting-notes to-do file. ## Keep it a terminal artefact Because the output format is fixed, do not attempt to feed the briefing into a further summarisation or reformatting stage. Either accept the shape or build the summarisation upstream. The practical consequence is that briefing quality tracks the quality of the underlying task data. If overdue items are not in the list, they will not appear, and no amount of formatting will recover them.
Quick Facts
Install
npx clawhub@latest install ai-daily-briefing