Making It Yours

Module 4: Making It Yours

A morning brief is only useful if it matches how you actually work. The structure in the previous modules is a starting point, not a prescription. This module covers the decisions you’ll make to adapt it — what to include, what the output should look like, and how the daily-prep companion closes the loop.

What to Include

The four integrations in Module 3 are calendar, tasks, email, news. But there are other things you might reasonably want in a morning brief:

• Daily note context — If you keep a daily note in Obsidian or a similar tool, the morning brief can read it. The obsidian read CLI command pulls a note by date. Anything you wrote yesterday that’s still relevant surfaces automatically.
• Specific projects — A working note for an active project can appear in the brief. “Here’s the current status of Project X” as a standing context block. Useful when you’re deep in something and want it foregrounded every day.
• Weather — Relevant if your day involves travel or outdoor plans. A quick weather lookup via a search tool adds one line.
• Financial signals — If you track invoices or cash flow, a quick scan of MoneyWiz data via the CLI can surface outstanding receivables. Optional and niche, but the integration is straightforward.

The test for inclusion: does this change what I do today? Calendar events do. Open tasks do. Email action items do. If an item wouldn’t change your priorities or your plan, it’s probably noise.

What to Skip

The temptation is to add everything. Resist it.

A morning brief that takes eight minutes to read has failed at being a brief. The goal is under three minutes: scan, absorb, begin. If you’re reading a news digest, you’ve turned the brief into a reading session.

News is the most common thing to skip or heavily limit. One to three headlines maximum. If you find yourself reading the full articles, cut the integration until you’ve developed the habit of treating it as signal-only.

Email triage at morning-brief time should surface action items, not summaries. If you want a full email digest, that’s a separate task. The morning brief gets the count of items needing action and the one or two that are urgent. Everything else can wait until the working email session.

Format Decisions

The default format — a dated header, then sections for each source — works for reading in a terminal or in a Claude Code output pane. But you might want different things:

Shorter output: Constrain each section to a fixed line count. Calendar gets five lines maximum. Tasks get ten. News gets three. Anything beyond the limit is truncated. Add this as an explicit instruction in the skill body.

Richer formatting: If you read the brief in a markdown-aware environment, you can use tables, badges, priority markers. The skill body can specify exactly what formatting Claude should use.

Spoken output: The brief can be formatted for text-to-speech — shorter sentences, no markdown symbols, natural phrasing. If you listen to your brief while making coffee, format it accordingly.

Saved to disk: Add a step at the end of the skill that writes the output to your daily note. obsidian append file="{date}" content="{briefing}". The brief becomes part of the permanent record of the day.

The Daily-Prep Companion

Morning-brief works better with a companion skill: daily-prep.

Where morning-brief looks at today, daily-prep looks at tomorrow. Run it at the end of the working day, usually just before closing up. It pulls tomorrow’s calendar, checks what tasks were completed today versus what was planned, and prompts you to set up the next day: what’s the priority, what needs to move, what’s the one thing that has to happen.

The output of daily-prep feeds into the next morning’s brief. A good night-before setup means the morning brief is confirming a plan rather than helping you assemble one. The mental model: daily-prep puts the pieces on the board; morning-brief tells you where to start.

The daily-prep skill lives at ~/.claude/skills/daily-prep.md. The pattern is the same as morning-brief but the sequencing is inverted: review today, plan tomorrow, close out.

The Compound Effect

A single morning brief is useful. A consistent one is transformative.

After two weeks of running the same skill every morning, you start to notice patterns. You can see when certain types of tasks cluster on certain days. You notice that Tuesdays are consistently meeting-heavy and low on focused work time. You start to plan around it.

The brief also creates a record. If you save it to your daily note (the obsidian append pattern above), you have a timestamped picture of what your days actually looked like — not what you thought they’d look like, but what was actually on your plate each morning. That’s useful data for weekly reviews and for understanding your own rhythms.

The social-briefing skill is a natural extension of this pattern. Where morning-brief covers your internal context — calendar, tasks, email — social-briefing covers your external positioning: what’s worth posting today, what’s happening in your areas of interest, what’s the one idea worth sharing. The two skills together take about ten minutes and replace what used to be a scattered 45-minute app circuit.

Running the Brief

The production morning-brief runs like this:

1. Open a new Claude Code session
2. Type /morning-brief or “give me my morning brief”
3. Wait about 60 seconds for the data gathering steps to complete
4. Read the output

That’s the full workflow. One command, structured output, clear head. The same discipline every morning.

The time you spend building this pays back on day one. Every morning after that is compounding return.

---

You’ve finished the course. The skill files go in ~/.claude/skills/. The AppleScript calendar queries are in Module 3. The task CLI commands are in Module 3. Start with calendar and tasks, run it for a week, then add the next source.

Your mornings are yours again.