Agent skill · Data & Analytics

live-artifact

Create refreshable, auditable Open Design artifacts backed by connector or local data. Trigger when the user asks for live dashboards, refreshable reports, synced views, or reusable data-backed artifacts.

nexu95,528★ · +2,037/wk · 5 repos on radarProfile →
claude-codecodexcursorApache-2.0
Install
npx skills add nexu-io/open-design --skill live-artifact --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 17
SKILL.md size: 9 KB
Bundled scripts: none
Path: design-templates/live-artifact/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 83,577 · +1,339 this week
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Live Artifact Skill Create an Open Design live artifact: a project-scoped, previewable HTML artifact whose data can later be refreshed without redesigning the presentation. ## Resource map ``` live-artifact/ ├── SKILL.md └── references/ ├── artifact-schema.md ← `references/artifact-schema.md`: artifact files, DTO shape, template binding rules ├── connector-policy.md ← `references/connector-policy.md`: connector safety, redaction, credential boundaries └── refresh-contract.md ← `references/refresh-contract.md`: source metadata, refresh execution, snapshots ``` ## 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 arti

What's inside
Steps it walks through
  1. Resource map
  2. Current status
  3. When to use this skill
  4. Workflow
  5. Required files
Ships with 16 files
  • assets/templates/clinic-console/README.md
  • assets/templates/clinic-console/data.json
  • assets/templates/clinic-console/template.html
  • examples/baby-health-live.html
  • examples/competitor-radar-live.html
  • examples/crm-table-live.html
  • examples/crypto-dashboard.html
  • examples/monday-operator-live.html
  • examples/stock-dashboard.html
  • examples/stock-portfolio-live/artifact.json
  • examples/stock-portfolio-live/data.json
  • examples/stock-portfolio-live/provenance.json
  • examples/stock-portfolio-live/template.html
  • references/artifact-schema.md
  • references/connector-policy.md
  • references/refresh-contract.md
More from open-design
All skills →
About this skill
What does the live-artifact skill do?

Create refreshable, auditable Open Design artifacts backed by connector or local data. Trigger when the user asks for live dashboards, refreshable reports, synced views, or reusable data-backed artifacts.

How do I install it?

Run `npx skills add nexu-io/open-design --skill live-artifact --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From nexu-io/open-design, a repository with 83,577 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going