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. 2026-10-27 addition: raw/Wait._Whaatttt..._Claude_LIVE_ARTIFACTS_Just_Dropped....md (Eliot Prince, launch-day video, 2026-04-22; see Launch Notes). 2026-10-28 addition: raw/Live_Artifacts_Just_10x_d_Claude_Cowork_Real_Use_Cases.md (Ben AI, 2026-04-27; see Ben AI’s dashboards and planning questions). 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. Update 2026-10-27: a no-code route now exists. Eliot Prince connects GSC and GA through Composio as a custom connector (2026-08 and 2026-10 videos); see Connectors and Claude SEO and AI-Search Project.
- Branded skill files keep dashboards on-brand. When a
brandedskill 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:
- 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 Claudecalls 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. - 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.
- 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.
- 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).
- 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.
- 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.
- 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.
- 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
- 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.”
Launch Notes (April 2026, Eliot Prince)
Source: raw/Wait._Whaatttt..._Claude_LIVE_ARTIFACTS_Just_Dropped....md, “Wait. Whaatttt… Claude LIVE ARTIFACTS Just Dropped…” by Eliot Prince, https://www.youtube.com/watch?v=xQ3lvqP57uA, 5:50, YouTube, published 2026-04-22. This is a launch-day video and predates the seven-recipe video above. Cowork has since moved to web and mobile (July 2026) and merged with chat into One Claude (September 2026), so the “desktop only” point below is historical.
- What launched: live artifacts, defined as “dashboards and live trackers connected to your apps, files, connectors that stay live in your account”. At launch they were “only available in the Claude Cowork desktop app”, under Live artifacts in the left sidebar.
- How Claude described them: interactive HTML pages that live in the Cowork sidebar, persist between sessions, “pull fresh data on demand” each time you reopen or refresh them, and stay interactive (filter, search, drill down).
- The built-in kickoff: “Create a live status page of what needs my attention today across all my connected tools and keep it updated.”
- The discovery meta-prompt (useful when you don’t know what to build): “I want to make a live artifact. Explain what live artifacts are in Cowork, then look at my connectors, ask me some questions, and figure out what’s going to be really useful for me.” For Eliot it proposed a daily briefing that pulls Notion tasks, Google Calendar and Gmail.
- The panel has history and export: previous runs (earlier days’ versions) and edit and download options.
- A dashboard from an MCP: one prompt naming his YouTube MCP produced a “YouTube morning dashboard”: a rolling 7-day window of views, watch time, new subscribers, retention, comments, traffic sources and top videos. Top-video names came out wrong on the first pass.
- Eliot’s framing: live artifacts solve “a lot of” what people had been building scheduled tasks for. That is his claim; the two still differ, because an artifact refreshes when opened and a task runs on a timer.
Ben AI’s dashboards and planning questions (added 2026-10-28)
Source: raw/Live_Artifacts_Just_10x_d_Claude_Cowork_Real_Use_Cases.md. Creator: Ben AI · URL: https://www.youtube.com/watch?v=PwLqKIGA25c · Duration: 11:49 · Platform: YouTube · Uploaded: 2026-04-27. Five days after launch; the limitations he lists were current then and some were announced as coming.
His dashboards (several built for team members rather than himself):
- Marketing conversions: YouTube + Bitly + PostHog, with tabs for conversions per video for three offers, bookings, the full funnel, openers and closers, and retention.
- Business intelligence: Stripe + PostHog (or Google Analytics) metrics plus AI-written strategy suggestions from the KPIs.
- Community intelligence: most common member issues from the week, pulled from Fireflies, support and his Circle community connector, with an in-artifact chat (“what specific problems did people have with the Obsidian setup?”).
- Customer support: draft a reply with AI or by hand and post it to Circle from the dashboard.
- Sales rep: inbox, calendar, PandaDoc proposal status and CRM deals, with deals movable from the dashboard.
- Former scheduled tasks: YouTube competitor intelligence (recent videos, who shipped what, keyword opportunities, breakout videos), a communications dashboard flagging items to answer across Slack, email and the community, and a second-brain dashboard of team to-dos.
How it differs from a scheduled HTML report. The artifact is built once; each refresh fills its data through the connectors instead of Claude regenerating the whole page, which Ben says is faster and more token-efficient. His advice: convert any scheduled task that only reports data (no actions) into a live artifact.
Why he thinks it matters: data from several tools in one view, a UI shaped to one person’s role, AI interpretation on top of the raw numbers, and, as actions mature, doing the work from the same page. He sees this as a step toward Claude as the main interface for work and a threat to some SaaS UIs and analytics tools (his opinion).
Limitations he reported (April 2026):
- Mostly visual: simple actions such as updating a CRM record can be built in, but skills cannot run inside an artifact.
- AI inside an artifact ran on Haiku only, by his account.
- No sharing across a team yet (Anthropic had announced it; compare the “Open in browser” signal under Recent signals).
- Slow with many connectors; he advises against pulling from around eight sources.
Questions to answer before building (from his “artifact planner” skill, which he sells; the questions themselves are in the video):
- What is the dashboard for?
- When and how often will you open it?
- Which connectors should it pull from?
- What data from each connector? Narrow it: broader MCP scope is slower and more error-prone.
- What should AI do with the data on each refresh (interpret, rank, prioritise)?
- Which brand guidelines should it follow?
- Which actions should it take? Define these up front, because they are hard-coded into the artifact.
- Do you want an AI chat over the data?
- What should it not do? He calls this the most important question, to stop a slow, oversized dashboard.
Answer them in one brain dump and ask Claude to “build a live artifact” from it; his skill first produces a brief to paste into the build chat.
How a Live Artifact Build Actually Runs
Pulled from the Competitor Move Tracker walkthrough (transcript lines 100-216) — the canonical first-time flow.
- 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.
- 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.).
- Claude reads skill files automatically. If you have a
brandedskill file in the workspace, Claude pulls colors / logos / fonts. No instruction needed. - 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.”
- Click Create (or Update if regenerating). The dashboard pops out on the right-hand side, then auto-pins to the top-left sidebar.
- 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
- 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.
- Open Cowork → Live Artifacts → New Artifact.
- Open Eliot Prince’s AI Recipe Vault (or the parent catalog entry for context) and copy the recipe prompt.
- Edit the business-context inputs at the top of the prompt (competitors, domains, currency, pipeline stages, etc.).
- Paste into the new artifact chat and run.
- If you don’t yet have a
brandedskill 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. - 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”). Partially answered 2026-10-27: the launch video says the artifact refreshes each time you open the page (“every time I log into this page, it’s going to refresh”). A timer-based refresh is still not shown. 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.
- Live Artifacts after One Claude. The sources describe a Cowork-specific “Live artifacts” sidebar entry. None of them says whether that entry survived the September 2026 merge of chat and Cowork, or how live artifacts relate to the unified artifacts and Claude Docs surfaces.
- Ben’s April 2026 limits. Haiku-only AI inside artifacts, no team sharing, and no skills inside artifacts were his observations five days after launch; the wiki has no later first-party source on any of them.
brandedskill 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.
Related
- Claude Cowork (Product Overview) — the parent surface that hosts Live Artifacts
- Cowork Getting Started — non-developer Cowork onboarding (Notion AI Recipe walkthrough)
- Cowork Jarvis Build — the rule-stacking AIOS that makes Live Artifacts smarter (knows your voice, projects, brand)
- Cowork “AI Consultant” recipe — Eliot Prince’s other Notion-vault Cowork recipe (4 knowledge files for client research)
- AI Recipe Vault — Eliot Prince’s Catalog — the parent vault that hosts the prompts referenced in this video
- Cowork Plugins — the Connectors/Plugins layer Live Artifacts depend on
- Cowork Marketing Skills Playbook (Ben AI) — Ben’s scheduled HTML reports that he later recommends converting into live artifacts
- Claude.ai Artifacts — the base primitive, including public sharing and multiplayer editing
- Cowork + Apify Scraping — Apify is the connector behind Competitor Move Tracker’s scraping
- Skill Design Patterns —
brandedskill file mechanism - R.I.T(E) Prompt Framework — the structure underlying the vault prompts
- A Business Dashboard You’ll Actually Use (Ben AI) — metric selection and a scheduled refresh skill.
- Agentic OS Command Center (Ben AI) — a live artifact as a second-brain dashboard, against two alternatives.
Recent signals
[Reddit signal — r/Anthropic 2026-05-27, u/Physical-Economist27] Source: raw/reddit-1tp6ihl.md. A Cowork user observed that today’s Claude Desktop update (macOS) added a new “Open in browser” right-click option on live artifacts, generating a real claude.ai URL with a clean human-readable slug:
claude.ai/cowork-artifact/<artifact-name>
Caveat at capture: the generated page renders blank/grey — the menu entry and the URL exist, but the page-load handler isn’t ready yet. Behavioral signal that shareable live artifacts are in flight for Cowork — consistent with the broader 2026 Cowork roadmap of bringing Cowork-built artifacts onto the public claude.ai surface. Watch the next Claude Desktop update for whether the page-render handler ships. If/when it does, expect the seven Eliot Prince dashboards above to become genuinely shareable links rather than Cowork-sidebar-pinned only.