Agent skill · writing content · nexu-io
live-artifact
Create refreshable, auditable OpenDesign artifacts backed by connector or local data. Trigger when the user asks for live dashboards, refreshable reports, synced views, or reusable data-backed artifacts.
Why this skill is useful
Provides specific workflows and commands for creating refreshable, auditable Open Design artifacts that the AI wouldn't reliably generate on its own.
What it needs
Requires shell installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 84,236 stars on the source repository.
What this skill does
Live Artifact Skill Create an OpenDesign live artifact: a project-scoped, previewable HTML artifact whose data can later be refreshed without redesigning the presentation. Resource map Current status Use the references in this directory as the source of truth for the live artifact file contract. Prefer daemon wrapper commands over raw HTTP when registering or updating live artifacts. When to use this skill Use this skill when the user asks for a data-backed view that should remain useful after the first render, for example a live dashboard, refreshable report, synced status page, auditable data view, or artifact that can later be refreshed from local/project data or connectors. Before creating files, decide whether the user actually wants a live artifact or a normal static artifact: Use a live artifact when the user mentions refresh, sync, recurring updates, connector-backed data, source/provenance tracking, dashboards, reports, or reusable data-backed views. Use a normal static artifact when the user only wants a one-off HTML/mockup/image/file and does not need refresh, source metadata, or data/provenance panels. If the intent is ambiguous, ask one short question: “Should this be refreshable/live, or just a static artifact?” Workflow 1. Resolve scope and data source without blocking on connected connectors Identify the preview goal, audience, data freshness expectations, and whether refresh should be possible later. If the user explicitly names a connector/source such as Notion, GitHub, Slack, or Google Drive, do not ask “where should the data come from?” before checking daemon connector tools. Prefer local/project sources or daemon connector tools when available. Do not call provider APIs directly when a daemon connector/wrapper exists. If connector data is needed, first list connectors with "$ODNODEBIN" "$ODBIN" tools connectors list --format compact. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nexu-io/live-artifact--ae0d8a