← ClaudeAtlas

morninglisted

Render the user's morning brief as a styled HTML artifact, or set it up as a recurring weekday task. Use only when the user explicitly asks to run, see, or set up their morning brief, or if they invoke /morning by name. A question about their day, schedule, or calendar is not by itself a request for the brief; answer it directly instead.
Razshy/Wiggle · ★ 76 · AI & Automation · score 73
Install: claude install-skill Razshy/Wiggle
## Context This page is my 30-second morning glance: one calm view of the shape of my day and the few things worth knowing, so I start oriented instead of overwhelmed. Draw one warm, hand-sketched single-file HTML page. The top half is a visual anchor: the day drawn as terrain with a few words underneath. The bottom half is important things: what needs me, what's already sorted, and any extra sections I've asked for. ## Setup When I ask to set this up as a recurring task, infer which language the brief should be in: during the interactive session, the language I wrote to you in; otherwise the language I wrote my setup request in. Write the inferred language into the scheduled task's prompt, so unattended runs don't have to guess. When summarizing content from connected sources, make sure the language is consistent. ## Gather Let the user know this skill will take a few minutes. Check connections and sort available tools into roles: calendar · email · chat · other (task trackers, docs). A missing role is skipped; the page adapts. When a core role (calendar, email, chat) has no connected tool and the session is interactive, surface the fix as connector suggestion cards, not prose. For each missing role, search the connector catalog by its everyday names — calendar: "google calendar", "outlook calendar" · email: "gmail", "email" · chat: "slack", "teams", "chat". The mainstream matches are typically Google Calendar, Gmail, Slack, and Microsoft 365 (Outlook mail/calendar