Overview
In this final guide, you will combine everything from the previous 17 articles — Projects, Styles, Skills, Connectors, Tasks, Cowork — into one polished system that delivers a personal AI morning briefing to your inbox every day before you've even opened your laptop.
Each previous article was about one tool. This one is about how the tools work together. The morning briefing is the perfect capstone because it touches every layer: a Project for your context, a Style for the voice, Connectors for live data, a Skill that defines the briefing format, a Task that runs it on a schedule, and Cowork to save the result somewhere durable. By the end of this guide, you'll have a working briefing system you can keep refining for years — and the architectural mindset to build any other multi-tool system you can imagine.
Who This Is Useful For
What You Will Build
A daily Personal Morning Briefing that arrives by email at 7:30 AM (or whenever you want), with:
The whole thing arrives in a single email. You read it in 3 minutes. Your morning starts focused, not reactive.
What You Need
Step 1: The Architecture
Before building, understand what each layer does:
You'll set them up bottom-up: context first, voice next, then data, then recipe, then trigger.
Step 2: Set Up the Briefing Project
If you already have a "Personal" Project from Article 03, use it. Otherwise create one named Daily Briefing.
Custom instructions:
This Project's job is to generate my daily morning briefing.
You know me as someone who wants:About me:
Lives in [your city]
Works as [role / industry]
Cares about [interests, hobbies — 3-5 specific things]
Family / important people: [names + relationships]
Health goals or constraints (optional): [...]
Current focus areas this quarter: [2-3 priorities] Briefing rules:
Always under 400 words total
Markdown formatting with clear section headers
Skip empty sections rather than padding ("nothing urgent today" beats fake content)
Be honest if there's nothing worth flagging in a section
Use Taiwan-style 繁體中文 for Chinese names and places; English for everything else unless I write to you in 中文
Project knowledge to add:
Step 3: Set the Style
Briefings without a defined Style come out sounding like LinkedIn newsletters. Pick or create one:
Briefing Voice description:
You are writing my daily morning briefing.Tone: clear, calm, slightly informal — like a smart friend sending me a message, not a corporate newsletter.
Rules:
Short sentences. Never use "I'd be happy to" or "Certainly!"
No filler ("As an AI assistant...", "Hope this helps!")
Use my name once at the top, never again
When mentioning a person, only use their first name
When mentioning a place, default to its local name (台北 not "Taipei City")
One small dry observation per briefing is welcome — like a friend noticing something. Not forced humor. Format: markdown, under 400 words, scannable.
Step 4: Verify Your Connectors
The briefing pulls from live sources. Verify each one works on its own first:
If any connector hesitates or asks for re-auth, fix it now. The Task in Step 6 will fail silently if a connector is broken.
Step 5: Build the Briefing Skill
This is the core recipe. Save as a Skill named morning-briefing.
Generate today's morning briefing.DATA TO PULL (in this order):
1. CALENDAR
- Read my Google Calendar for today
- List every event with time, title, and one-line context (who, where if relevant)
- Flag anything before 9 AM, anything that requires travel, and anything I might want to prep for
2. INBOX
- Read unread Gmail from the past 24 hours
- Filter out: newsletters, marketing, automated notifications
- Surface up to 5 emails worth my attention, with:
- Sender (first name)
- Why it matters in 1 line
- Suggested response approach (reply now / batch later / no action)
3. PRIORITIES
- Read my Notion "Daily Priorities" page
- List the top 3 things I said matter this week
- For each, suggest one small action I could do today to advance it (max 15 min)
4. NEWS
- 3 headlines, each in 1 sentence with a source link:
- One Taiwan-related
- One world / international
- One in my interest area (technology, food, design, whatever's in my Project context)
5. WEATHER
- Today's forecast for [my city]: temperature range, rain chance, any warnings
- One sentence on whether I should bring an umbrella or dress differently than usual
6. ONE REFLECTION
- Pick ONE of: a question worth sitting with, a relevant quote, or a nudge based on patterns in my recent emails and calendar
- Don't suggest an answer. Just deliver the reflection.
OUTPUT FORMAT:
Use markdown headings (## for each section).
Order: Today at a Glance (calendar + weather), Inbox, Priorities, Quick Wins, News, Reflection.
Total: under 400 words. If a section has nothing to report, say so in one line rather than padding.
End with a single line: "Have a good one." (no other sign-off)
Test it. In your Daily Briefing Project, with Briefing Voice Style on, run /morning-briefing manually. Read what comes out. Adjust the Skill until version 1 feels right (it won't be perfect; that's fine).
Step 6: Schedule It
Settings → Scheduled Tasks → + New Task.
Prompt: simply /morning-briefing (the Task triggers your Skill)
Schedule: Daily at 7:30 AM (or 30 minutes before you usually wake up)
Delivery: Email to your primary inbox
Project: Daily Briefing (so it picks up your context)
Style: Briefing Voice
Save. Click Run now to test the full pipeline. The email should arrive in your inbox within 90 seconds.
Step 7: Save Every Briefing to Your Computer (Cowork)
Optional but excellent: have Cowork save a copy of every briefing as a markdown file on your computer, organized by year/month/day.
Make a folder: ~/Documents/MorningBriefings/. Point Cowork at it.
In Cowork, build this Skill (save-briefing):
Take the most recent briefing email I received from Claude (today's morning briefing).Save it as a markdown file in this folder, with the path pattern:
YYYY/MM/YYYY-MM-DD.md
(So today's briefing goes to 2026/05/2026-05-07.md)
If the year or month folder doesn't exist, create it.
Schedule this Cowork task to run at 7:45 AM daily — 15 minutes after the briefing arrives. Now you have a permanent local archive of every morning, searchable and offline-readable.
Step 8: The First Week — What to Refine
Day 1's briefing won't be perfect. Use the first week to refine:
After two weeks, the briefing should feel uniquely yours. If it still feels generic, the issue is almost always in the Project context (Step 2) — go back and add more specifics about who you are and what you care about.
Step 9: Add Optional Power-Ups
Once the basic system is humming, layer in advanced features:
Going Further
Build an "evening review" companion. Same architecture — different Skill. End-of-day summary at 9 PM: what you actually got done, what didn't happen, one thing you'll do differently tomorrow. Pairs beautifully with the morning briefing.
Build a Sunday weekly briefing. Even higher-level: what happened this week, what's coming next week, one big-picture question. Run it Sunday at 7 PM.
Apply the architecture to other systems. The same pattern (Project + Style + Connectors + Skill + Task) builds any recurring multi-tool system: a weekly KPI report, a monthly journal compilation, a quarterly self-review, a daily learning prompt. The architecture transfers.
Key Takeaways
Here's what you learned in this final guide:
The morning your first auto-generated briefing arrives — and you read it on your phone before getting out of bed — is the moment everything you learned in this series clicks. The 18 articles weren't separate features; they were one toolkit, leading to this.