Agent skill · Databases

live-dashboard

Notion-style team dashboard rendered as a Live Artifact. A single-page, self-contained HTML dashboard with KPIs, a 7-day sparkline, a real-time activity feed and a linked-database task table — wired to Notion via the Composio connector catalog. Refreshes on demand and when the artifact is opened. Falls back to seeded mock data when no connector is bound, so it works offline / in screenshots / in the picker preview.

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

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

Facts
Files in the skill folder: 7
SKILL.md size: 8 KB
Bundled scripts: none
Path: design-templates/live-dashboard/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 Dashboard You are a senior product-designer-engineer building a **Live Artifact** — an HTML page that behaves like a working dashboard, not a mockup. Your output ships, not only renders. ## Pre-flight (must complete before emitting any HTML) 1. `Read assets/template.html` — start from this skeleton verbatim. Do not rebuild the shell from scratch. Override only what the user's brief or the active DESIGN.md require. 2. `Read references/layouts.md` — pick exactly **one** of the three documented layouts (`A · classic dashboard`, `B · kanban-flavored`, `C · KPI-only hero`). State your choice in your reply. 3. `Read references/components.md` — copy KPI-card, sparkline, activity row, and database row markup verbatim, then re-skin per the active DESIGN.md. Do not invent new component shapes. 4. `Read references/connectors.md` — only when `inputs.connector !== mock`. Emit a sibling `connectors.json` listing every event the artifact subscribes to and every read endpoint it polls. 5. `Read references/checklist.md` — every P0 row must be true before you emit `index.html`. Quote each P0 row inline in your reply with `[x]` or `[ ]`. Do not emit while any P0 is unchecked. ## Build order 1.

What's inside
Steps it walks through
  1. Pre-flight (must complete before emitting any HTML)
  2. Build order
  3. Live behavior (the part that earns the "Live" in Live Artifact)
  4. Self-critique (must run before emitting)
  5. Hard nos (anti-AI-slop)
  6. Output contract
Ships with 6 files
  • assets/template.html
  • example.html
  • references/checklist.md
  • references/components.md
  • references/connectors.md
  • references/layouts.md
More from open-design
All skills →
About this skill
What does the live-dashboard skill do?

Notion-style team dashboard rendered as a Live Artifact. A single-page, self-contained HTML dashboard with KPIs, a 7-day sparkline, a real-time activity feed and a linked-database task table — wired to Notion via the Composio connector catalog. Refreshes on demand and when the artifact is opened. Falls back to seeded mock data when no connector is bound, so it works offline / in screenshots / in the picker preview.

How do I install it?

Run `npx skills add nexu-io/open-design --skill live-dashboard --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