Live Today Status Page (Claude Cowork)

Build me a live "today" status page as a Cowork artifact that surfaces what needs my attention across all my connected tools, with actions wired in where the APIs allow.

Before you write any code, do this in order:

1. ENUMERATE my connectors. List every MCP server / connector I have available and group the tools by domain (calendar, email, money, content, files, meetings, CRM, analytics, etc.). Tell me what you found in one short paragraph — no tables, no fluff.

2. CHECK FOR BRAND. Look at my available skills and project files for anything that defines my brand: a brand-baseline skill, brand-guidelines doc, style guide, or company-named skill. If you find one, load it and use its colors, fonts, and voice. If you don't, default to a professional modern style: off-white background, near-black text, one accent color, generous whitespace, system fonts, hairline borders, minimal cognitive load. Confirm to me which path you're taking in one line.

3. ASK ME, USING THE ASK-USER-QUESTION TOOL (multiple-choice), until you have enough to build something I'll actually use. Don't ask in plain text — use the structured tool. Cover at minimum:
   - Which domains matter most for "today" (pick top 3-5 from what you found)
   - Whether I want financial data on the page (if Stripe/QuickBooks/Xero is connected)
   - How aggressive to be on filtering (e.g. unread email = last 24h vs 7d)
   - Whether destructive actions should be one-click or require confirm
   - My timezone if it's not obvious from the data
   - Anything specific I'd want to action from the page (delete, send, archive, schedule, mark done)
   Stop asking once you have what you need. Don't drown me in questions.

4. PROBE every connector you plan to use with one real call each, so you see the actual response shape — not what you assume from the schema. Tell me anything surprising or anything that's empty / broken.

5. SUGGEST what's possible. Before building, give me a short list of 3-6 sections you propose, each with: what it shows, what action I can take from it (with the actual tool name), and whether the API supports that action. If an obvious action isn't possible because the connector lacks a write tool, say so out loud — don't fake buttons that don't work.

6. BUILD the artifact via create_artifact. Requirements:
   - Self-contained HTML, light mode, brand or fallback design system
   - Pulls fresh data on every open via window.cowork.callMcpTool
   - KPI strip up top with the most important numbers
   - Sections in priority order, each a card
   - Real action buttons wired to MCP tools where supported (confirm() before destructive)
   - Empty states that say something useful, not just "no data"
   - Errors handled per-section so one broken connector doesn't kill the page
   - Honest about what's not actionable — link out to the source app instead of hiding it

7. AFTER BUILDING, tell me in plain language: what's wired, what's read-only, what surprised you in the data, and the single most important thing on the page right now.

Push back if I ask for something a connector can't actually do — don't pretend. Keep your responses short. Real language. No emoji unless I use them first.

Copy the block above straight into your AI tool — anything in [BRACKETS] is yours to fill in.