I replaced three morning routines with one skill
I was starting every day running the same three things in Rebel: meeting prep, client Slack monitoring, and email triage. Three separate automations, three separate Actions items, and I’d be reading them in order anyway. It was working, but it felt fragmented.
So I built a “Start My Day” skill that chains all three into a single parallel run. Each stream collects its findings internally, then everything gets synthesised into one unified briefing in my Actions inbox: top 3 priorities first, then meetings, Slack by channel, emails needing action, and a waiting-on list at the bottom.
The key design decision was suppressing individual inbox items from each sub-skill and only surfacing the consolidated one. The skill files for meeting prep, Slack monitoring, and email triage still do all their work (Rebel saves meeting notes, applies Gmail labels, etc.) - they just don’t create inbox noise anymore.
What I didn’t expect: forcing the synthesis step made me think harder about prioritisation logic. I ended up writing a clear hierarchy into the skill - unanswered client Slack messages beat urgent emails, which beat meetings starting in under 2 hours. Without the synthesis requirement, I’d never have made that explicit.
The whole thing runs at 8am on weekdays. Takes about 2 minutes to read top to bottom. One item in my inbox instead of three.