The Rundown

In this guide, you will learn how to turn your daily updates into a personalized Morning Edition in Claude. This is useful because you get one ranked brief instead of bouncing between Slack, Gmail, Notion, and your calendar every morning.

Who This Is Useful For

• Operators and founders who start the day in five different tabs and want one clean brief
• Managers and team leads who need action items, meeting prep, and internal updates in one place
• Anyone already running agents or reports who wants Claude to assemble the final edition instead of doing all the research itself

What You Will Build

You will build a static newspaper-style daily brief that pulls together your most important updates, then turns into a reusable skill and scheduled task.

This is the front page. You will prompt Claude to turn your last 24 hours into a clean cover story with inbox, Notion, calendar, and Slack summaries.

This is the inbox section. Claude pulls your Gmail updates into a readable dispatch with clear priorities instead of one long summary blob.

This is the research section. If you already keep AI reports or task lists in Notion, Claude can fold those into the same edition.

This is the automation layer. Once the skill works, you will schedule it to run every morning in Claude CoWork.

What You Need

• Claude or Claude CoWork
• Slack, Notion, Gmail, and Calendar connected if you want the full version
• Optional: a centralized task list or daily AI reports database in Notion
• A few minutes to refine the first draft before you automate it

Pro tip: Start with connected work tools you already trust. If you are testing with sensitive data, use sample content first.

Step 1 Connect Your Sources

Open Claude or Claude CoWork and make sure your integrations are connected.

You want access to:

• Slack
• Notion
• Gmail
• Calendar

If you already keep a central task list or a daily AI reports database in Notion, connect that too. That is where this gets better. Claude stops acting like a researcher and starts acting like an editor.

Step 2 Create the First Morning Edition

Now prompt Claude to make the paper.

Use a prompt close to the one from the video guide:

Take a stab at making me a quick morning newspaper called Morning Edition.

It should update me on:
- my Slack updates
- my Notion updates
- my Gmail updates
- my calendar updates

Use the last 24 hours.
Make it a static newspaper, not a live artifact.
Format it like a newspaper with top stories, action items, and schedule prep.

That "last 24 hours" instruction matters. It keeps the edition focused. The other important instruction is "static newspaper, not a live artifact." You want something you can keep, review, and compare over time.

Pro tip: If Claude gives everything equal weight, ask it to make stronger editorial choices. Action items and calendar prep should beat random reading.

Step 3 Refine It and Turn It Into a Skill

Once Claude gives you a first version:

• review the layout
• cut weak sections
• fix the order
• make the important items more prominent

Then tell Claude:

Turn this process into a skill.

Claude will package the workflow so you can run it again without rebuilding the prompt every time.

Pro tip: Do not waste Opus on this if your reports are already gathered upstream. In the demo, the better move was Sonnet or Haiku, because the hard work had already been done.

Step 4 Schedule It in Claude CoWork

After the skill is saved, go to Claude CoWork and create a recurring task.

Your instruction can be simple:

Run /morning-edition every morning.

If you want delivery built in, use:

Run /morning-edition and then email it to me at [your email].

If Slack or email is connected, you can have the edition delivered there. Otherwise, it will show up in a new Claude CoWork thread.

The nice part is that once the skill is stable, the morning brief becomes a product, not another prompt you have to remember.

Going Further

The best version of this workflow is not one model doing everything from scratch.

Use other agents and automations to gather outside news, AI reports, customer notes, or workflow updates first. Drop those into a Notion database. Then let Claude read those reports and assemble the final paper.

That is the real strategy:

• let other systems do the research
• let Claude do the editing
• separate analysis from assembly

That setup is less fragile, cheaper to run, and easier to improve over time.