Module 1: The Daily Dashboard Problem

Here is what the first 45 minutes of most knowledge workers’ days looks like.

Open email. Scan subject lines. Flag two things. Get distracted by one. Open calendar. Check what’s happening today. Notice a conflict. Open tasks. Look at the list. Feel vague dread. Open Slack. Catch up on overnight messages. Find one thing that changes your priorities. By the time you’ve finished, it’s nearly 9am, you haven’t done any real work, and you’re already reactive.

This isn’t a discipline problem. It’s a systems problem. Each tool holds a fragment of your context. You are the integration layer, manually assembling the picture every morning from separate sources.

The Cost Is Hidden

The 45 minutes is visible. What’s less visible is the cognitive cost of the switching itself.

Each app switch resets your mental context. You finish email feeling like you understand your inbox. Then you open tasks and have to re-establish what matters. Then Slack resets you again. By the time you sit down to actually work, you’ve done five context switches and you haven’t produced anything. The morning scan feels productive because it’s activity. It isn’t.

The other hidden cost is inconsistency. On some days you have time for the full circuit. On others you shortcut it and miss something. The briefing quality varies with how rushed you are — which is exactly when you most need it to be complete.

What the Alternative Looks Like

Every morning, before I start work, I run a single command. Within a minute I have:

• Today’s calendar events, with start times
• Outstanding tasks from my task manager
• An email scan: what needs action, what’s noise
• A quick news check filtered to topics I care about

The output is structured, consistent, and ready to read. It takes under five minutes from command to clear head.

That’s what the morning-brief skill does. It’s not a dashboard app. It’s not another tool to log into. It’s a Claude Code skill that orchestrates four data sources — calendar, tasks, email, news — and returns them as a single briefing in whatever format works for me.

Why a Skill and Not an App

You could buy a morning dashboard app. Several exist. The problem with apps is that they are someone else’s idea of what a morning briefing should look like.

A skill you build yourself is different. You decide what goes in. You decide what format the output takes. You can add a data source that no app would ever integrate — your own daily notes, a specific Slack channel, a personal tracking spreadsheet — because you control the integration points.

The other advantage: a skill built on top of Claude Code uses the same tools and patterns as the rest of your AI system. The calendar lookup in morning-brief is the same AppleScript pattern you might use in a scheduling agent. The email scan is the same mail-triage pattern used elsewhere. Everything composes.

What This Course Builds

By the end of four modules, you’ll have a working morning-brief skill that:

• Pulls your calendar events for the day via AppleScript
• Scans your task manager for open items
• Runs a quick email triage to surface action items
• Checks a news source for anything relevant to your work
• Returns all of this in a consistent, readable format

Module 1 (this one) sets up the problem. Module 2 builds the core skill. Module 3 covers each data source in detail — how they work, where they can fail, how to adapt them for your setup. Module 4 covers customisation: what to include, what to skip, and how the daily-prep companion skill closes the loop the night before.

The skill in production runs in under 60 seconds. The time you spend building it pays back on the first day.

---

The next module builds the briefing from scratch.