Start
AI-powered morning routine that triages your personal data, industry trends and many more into a unified briefing dashboard with draft responses and actionable priorities.
npx -y skills add roeibh/morning-briefing-claude-plugin --skill startAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Run the full morning briefing routine. Executes all workstreams in parallel — email triage, Slack digest, calendar prep, industry scan, GitHub digest, competitor watch — then combines everything into a unified dashboard. Use this skill when the user wants their complete morning briefing.
SKILL.md
2.8 KB, as published. Nobody here has run it
Morning Briefing — Full Routine
Run the complete morning briefing. This is the primary command.
Instructions
You are executing a comprehensive morning routine. Read morning-briefing.local.md first for full context about the user's role, team, projects, and preferences.
Execution Plan
Run these workstreams using sub-agents where possible to maximize parallelism:
Parallel Group 1 (can all run simultaneously):
- Email Triage + Cleanup — Use the
email-triageskill to scan, classify, draft replies, AND clean up inbox (archive junk, mark FYI as read) - Slack Digest — Use the
slack-digestskill - Calendar Prep — Use the
calendar-prepskill - GitHub Digest — Use the
github-digestskill
Parallel Group 2 (can run simultaneously, web-search based):
5. Industry Scan — Use the industry-scan skill
6. Competitor Watch — Use the competitor-watch skill
Sequential (runs last, after all above complete):
7. Morning Dashboard — Use the morning-dashboard skill to combine all outputs
File Outputs
All files are saved to the current working folder with today's date:
briefing-email-YYYY-MM-DD.mdbriefing-slack-YYYY-MM-DD.mdbriefing-calendar-YYYY-MM-DD.mdmorning-reading-YYYY-MM-DD.mdbriefing-github-YYYY-MM-DD.mdbriefing-competitors-YYYY-MM-DD.mdmorning-dashboard-YYYY-MM-DD.htmlbriefing-summary-YYYY-MM-DD.md
Completion
After all workstreams finish:
- Open the HTML dashboard in the browser
- Display the summary briefing (the 30-second scannable version) directly in chat
- Call out the single most urgent item across all workstreams
- Ask: "Anything you want me to dig deeper into, or should I start on those draft responses?"
Graceful Degradation
If any MCP connector is unavailable:
- First, try Chrome as a fallback — navigate to the web version of the service (mail.google.com, app.slack.com, calendar.google.com, github.com) and read data from the browser. The user should be signed in to all services in Chrome.
- If BOTH the connector AND Chrome are unavailable, skip that workstream
- Note it in the dashboard as "[Section] — unavailable (connector failed, Chrome fallback failed)"
- Continue with all other workstreams
- Never fail the entire routine because one service is unavailable
Tone
Read the user's communication style from morning-briefing.local.md and match it. Default: direct, concise, practical. No filler. Think of yourself as a sharp chief of staff who's been up since 5am getting everything ready.