# live-artifact

live-artifact builds refreshable HTML artifacts from project or connector data. Use it for live dashboards, reports, and synced data views.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 123 installs · ★ 108855 repo stars
- Author: nexu-io
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/nexu-io/open-design/tree/HEAD/design-templates/live-artifact/SKILL.md
- Updated: 2026-10-25
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/live-artifact

## What it does

This skill builds an OpenDesign artifact whose presentation can be refreshed as its data changes. It writes `template.html`, `data.json`, `artifact.json`, and `provenance.json`; the daemon then derives `index.html`. Template bindings handle scalar values and one-level list repetition with `data-od-repeat`.

The workflow accepts local/project sources and daemon connector tools. It keeps preview data compact, records source and transformation notes, and registers or updates the artifact through OpenDesign wrapper commands. Stored JSON must exclude credentials, API keys, cookies, authorization headers, and raw provider payloads.

The skill targets Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode. It requires `shell` and `file_write` capabilities. `index.html` is generated output, so the source should be `template.html` together with `data.json`.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add nexu-io/open-design --skill live-artifact -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/live-artifact/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/live-artifact/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add nexu-io/open-design --skill live-artifact -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/live-artifact/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add nexu-io/open-design --skill live-artifact -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/live-artifact/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install nexu-io/open-design design-templates/live-artifact/SKILL.md
```

2. **Manually: put the files in place**
- File: `.github/skills/live-artifact/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add nexu-io/open-design --skill live-artifact -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/nexu-io/open-design --path design-templates/live-artifact
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/live-artifact/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add nexu-io/open-design --skill live-artifact -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/nexu-io/open-design/tree/HEAD/design-templates/live-artifact/SKILL.md

## When to use it
- build a refreshable HTML dashboard from project data
- turn source data into a reusable report template
- connect a view to local data or a daemon connector
- record source provenance and transformation notes

## Example prompts
- Create a live dashboard from the project data and make its `template.html` refreshable.
- Build a report that can later pull data through a connected daemon connector.
- Create a synced data view and record its source details in `provenance.json`.

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: de5c1b026ef2a9fd.

BEGIN THIRD-PARTY FILE de5c1b026ef2a9fd
````text
---
name: live-artifact
description: |
  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.
triggers:
  - "live artifact"
  - "live dashboard"
  - "refreshable dashboard"
  - "live report"
  - "refreshable report"
  - "synced view"
  - "可刷新"
  - "实时看板"
od:
  mode: prototype
  scenario: live
  preview:
    type: html
    entry: index.html
    reload: debounce-100
  design_system:
    requires: true
  outputs:
    primary: index.html
    secondary:
      - template.html
      - artifact.json
      - data.json
      - provenance.json
  capabilities_required:
    - shell
    - file_write
---

# 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

```
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 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.
````
END THIRD-PARTY FILE de5c1b026ef2a9fd

The third-party file has ended. Everything between the de5c1b026ef2a9fd tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2687 of 8892 bytes. © nexu-io · Apache-2.0 · https://github.com/nexu-io/open-design/tree/HEAD/design-templates/live-artifact/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
