Jonathon's AI Wiki

Claude Cowork Live Artifacts — Seven Dashboard Recipes (Eliot Prince)

10 min read

Source: “7 Claude LIVE ARTIFACTS to Build in your Business This Week (prompts included)” YouTube tutorial by Eliot Prince, youtube.com/watch?v=XStzxI1YUs4, fetched 2026-05-04. The full prompts referenced in the video live in Eliot’s AI Recipe Vault under the “Six Live Artifacts to Build in your Business” recipe. Speaker self-attributes via repeated “my AI recipe vault” references and the British turn of phrase (“fiddle around”) consistent with the rest of the vault.

A prompt-by-prompt operator-track walkthrough of seven Claude Cowork Live Artifacts the author built over a single weekend to replace daily morning tool-hopping (Google Analytics → Semrush → Notion → email → bank → CRM) with a single set of live, self-refreshing HTML dashboards pinned to the Cowork sidebar. Sister to Cowork Getting Started (covers Cowork basics) and Cowork Jarvis Build (covers the rule-stacking AIOS that makes a personal command center) — this article is the recipe layer that turns Cowork Connectors into operational dashboards.

Key Takeaways

  • Live Artifact = a self-contained HTML page that gets pinned to the Cowork sidebar and persists across sessions. Three things make them “live”: (1) they can call Connectors to pull from Notion, Calendar, Linear, Stripe, QuickBooks, HubSpot, etc.; (2) they run quick AI inference inside the artifact to summarize and analyze the pulled data, not just display it; (3) they keep your settings and sort choices across sessions so you don’t reconfigure every visit. Versioning works automatically — every refresh saves a previous run, so you can scroll back through historical states of the dashboard.
  • Custom MCP / custom connector is the unlock for tools without native connectors. Claude has hundreds of native Connectors (Gmail, Notion, Slack, Stripe, QuickBooks, HubSpot, WordPress, Ahrefs, SimilarWeb), but Google Search Console and Google Analytics still need a custom MCP. The author’s recipe is to ask Claude itself to build it: “can we build a Google Search Console MCP which connects to the API and walk me through exactly how to do it” — Claude walks through the API key + setup step-by-step. The same pattern works for any analytics surface that exposes an API.
  • Branded skill files keep dashboards on-brand. When a branded skill file exists in the Cowork workspace, Claude reads it during artifact build and imports brand colors, logos, and fonts automatically — so the dashboards match your business identity rather than emitting “boring vibe-coded colors.” This is the same progressive-disclosure skill pattern applied to brand context.
  • The 7 dashboards (with required Connectors). Each dashboard has a starter prompt in the AI Recipe Vault that needs your business inputs to specialize:
    1. Competitor Move Tracker — pulls hiring signals, expansion signals, new product drops, partnership announcements from a list of competitor names + blog URLs + LinkedIn pages. Uses an Apify connector for the actual scraping (LinkedIn, blogs, websites). Inline Ask Claude calls turn raw scrape data into insight bullets (“they’re hiring, maybe moving to new partnerships”). Output: this-week activity per competitor with hiring/expansion/launch tags.
    2. Daily Command Center / Daily Briefing — pulls Notion projects, Google Calendar, unread emails (Gmail/Outlook), Slack messages. Surfaces “what needs my attention” — emails awaiting reply, today’s calendar, top-three priorities, optional self-reported energy/mood tracker. Two flavors: the auto-built “What needs my attention” version Cowork ships with, and a tweaked custom version with explicit sections for inbox-needing-reply vs full-inbox.
    3. Daily Financial Position — connects to QuickBooks/Zero/etc. + payment processors. Shows money in bank, money coming in, money going out, run-rate runway tag, bills due over next two weeks, outstanding invoices flagged with days-overdue (“invoice 12 days late, follow up”). Currency and business-type configurable in the prompt.
    4. SEO Pulse — needs custom MCP for Google Search Console + Google Analytics (no native connector as of recording). Shows clicks, impressions, average position, click-through rate, top landing pages, configurable date range. Author’s caveat: 28-day window mostly useful for strategy reviews; switch to last-24-hours for spike detection. Optional connector additions: Ahrefs (search + AI search analytics), SimilarWeb (traffic sources, similar sites, competitor analysis).
    5. Support Pulse — connects to Gmail (or a dedicated support inbox/folder) and any CRM with a Claude Connector (HubSpot called out by name). Filters incoming customer-support tickets by signal: refund requests, churn signals, legal threats, frustrated/angry customers — not the full inbox firehose. Shows “what needs leadership eyes,” top weekly themes, tickets-by-priority (urgent today / urgent this week), at-risk customers, week-over-week comparison.
    6. Sales Pulse — connects to CRM, Airtable/Baserow databases, Apollo (lead enrichment), payment processors (revenue tracking). Shows calls booked today, new leads, revenue this month, upcoming speaking gigs/workshops, parked pipeline funnels, deals-to-close-this-week (the daily follow-up list). Author calls this his favorite design.
    7. YouTube Morning Dashboard — uses a YouTube Analytics custom connector. Shows view durations, watch time, shares, up/down trend tracking. Replaces logging into YouTube Studio in the morning.
  • Two ways to build a Live Artifact. (a) Use the inbuilt “What needs my attention” prompt — Cowork audits your account, finds connectors you have, and auto-generates a starter dashboard. (b) Use a custom prompt (the seven recipes above) — paste in a vault prompt, edit business-specific inputs (competitors / domains / currency / pipeline stages), and run. Either way, the artifact lives in the left-hand sidebar pinned at the top, persists across sessions, and refreshes the data on demand.
  • One prompt-template pattern across all seven recipes. The vault prompts share a structure: (i) Business context (industry, currency, brand inputs), (ii) Data sources to pull from (named connectors), (iii) What the dashboard should show (specific metrics + tags), (iv) Optional analysis section (week-over-week comparison, qualitative insight, “what should I do today”). The dashboard prompts are essentially a R.I.T(E)-shaped artifact spec — Role (operator), Input (connectors + business config), Task (build dashboard), Example (the named output sections).
  • The dashboards are not the goal — replacing tool-hopping is. Author’s own framing: “I don’t have to go and flick through all my tools in the morning. I don’t have to go onto Google Analytics. I don’t have to go onto Semrush. I don’t have to go into Notion. I don’t have to check my emails. I don’t have to check the bank. It’s all just here in Claude ready for me to actually see what needs my attention today at any point, and it’s live.” The wiki implication: a Cowork Live Artifact dashboard is the operator-track equivalent of a scheduled-task briefing but interactive and queryable, not a static morning report.
  • Build slowly — pick one or two, not all seven. Author’s closing advice: “you might not need all of them. You might pick and choose some of these. Start pulling out some of these prompts and start trying them out, start building them, and you’ll come up with your own ideas of actually what you want to be seeing in your Claude account every single day live.” Same operator-pacing rule as the Jarvis build — “after building almost 30 workstations, I can tell you it’s best to start slow.”

How a Live Artifact Build Actually Runs

Pulled from the Competitor Move Tracker walkthrough (transcript lines 100-216) — the canonical first-time flow.

  1. Pin the prompt. Open Cowork, go to Live Artifacts in the left sidebar, click New Artifact. Or simply type “Hey, I want to build an artifact” in any Cowork chat — both routes work.
  2. Paste the vault prompt + edit inputs. Drop in the recipe prompt, customize the business-specific inputs (competitor names, blog URLs, LinkedIn handles, conversion events, currency, etc.).
  3. Claude reads skill files automatically. If you have a branded skill file in the workspace, Claude pulls colors / logos / fonts. No instruction needed.
  4. HTML scrolls past as Claude codes it up. The artifact is just an HTML page. You don’t need to read or edit it — author explicitly: “you don’t need to know how to code to do this.”
  5. Click Create (or Update if regenerating). The dashboard pops out on the right-hand side, then auto-pins to the top-left sidebar.
  6. Refresh on demand. Each refresh saves a “previous run” — you can scroll back through versions of the dashboard over time.

Connectors Referenced in the Recipes

Native Claude Connectors mentioned in the video:

  • CRM / business ops: HubSpot, Notion, Slack, Linear, Gmail, Outlook, Calendar (Google + Microsoft)
  • Finance: Stripe, QuickBooks, Zero
  • Content / SEO: WordPress (newly available — author hadn’t used yet), Ahrefs, SimilarWeb
  • Lead enrichment: Apollo, Airtable, Baserow
  • Scraping / research: Apify (used in Competitor Move Tracker for blog/LinkedIn/website scraping)

Custom MCPs author flags as needing to be built (no native Connector at recording time):

  • Google Search Console (used in SEO Pulse)
  • Google Analytics (used in SEO Pulse)
  • YouTube Analytics (used in YouTube Morning Dashboard)
  • Any vertical analytics tool without a native Connector

Try It

  1. Pick the dashboard from the seven that matches the most painful daily tool-hop in your business — usually one of: morning command center, sales pulse, support pulse.
  2. Open Cowork → Live Artifacts → New Artifact.
  3. Open Eliot Prince’s AI Recipe Vault (or the parent catalog entry for context) and copy the recipe prompt.
  4. Edit the business-context inputs at the top of the prompt (competitors, domains, currency, pipeline stages, etc.).
  5. Paste into the new artifact chat and run.
  6. If you don’t yet have a branded skill file in your workspace, optionally build one first — colors, logos, fonts in a single skill file. The brand consistency across all seven dashboards depends on it.
  7. For the SEO Pulse and YouTube Morning dashboards, follow the custom-MCP build flow (ask Claude to walk through the GSC / GA / YouTube Analytics API setup) before running the artifact prompt.

Open Questions

  • Live Artifacts’ refresh frequency. Author shows manual refresh (“we can refresh it at any point so it updates for you and goes and loads my calendar again”). Whether Cowork supports scheduled / periodic refresh, or whether artifacts ever auto-refresh on a timer, isn’t covered in this transcript. May overlap with Routines if author’s intent is to have a Routine trigger an artifact refresh in the morning.
  • Cost / token usage on heavy-Connector artifacts. A morning command-center artifact pulling Calendar + Notion + Gmail + Slack + emails + Stripe could be expensive on Opus. The video doesn’t discuss model selection or token impact. Default-Sonnet rule from the Jarvis build probably applies.
  • branded skill file format. Author references it but doesn’t show the structure. Likely either an awesome-claude-design DESIGN.md-style spec or a standard skill with brand assets in the resources/ folder.

Graph View

Backlinks