Skip to content

Guide · Agent skill

How to use the Live Team Dashboard agent skill

Updated · written with AI from the project's own documentation and checked against our catalogue data

The live-dashboard skill tells a coding agent to build one self-contained HTML page styled like Notion, with headline numbers, a 7-day trend line, an activity feed and a task table. It is meant to behave like a working status page rather than a static mockup. This guide explains what the skill does, how to install it, how to ask for a dashboard in plain language, and what to check before you trust the numbers.

Live Team Dashboardnexu-io/open-design · Apache-2.0

Quick start

  1. 1Download and unzip the skill. Download the ZIP from this page and unzip it so the live-dashboard folder contains SKILL.md. Put it in ~/.claude/skills/ for all projects or in .claude/skills/ for one project.
  2. 2Or upload it in the Claude apps. In the Claude apps, open Settings, go to Capabilities, then Skills, and upload the ZIP.
  3. 3Make sure the agent can write files. The skill needs an agent that can write files and make surgical edits, as it requires file_write and surgical_edit capabilities.
  4. 4Ask for the dashboard. Describe the workspace and the KPIs you want, using a phrase such as 'team dashboard' or 'ops dashboard'.
  5. 5Choose data source. Use mock for sample data, or bind a Notion connector through the Open Design daemon for real data.
  6. 6Review and refresh. Open index.html, press Refresh, and check the status pill and footer before sharing.

What the live-dashboard skill makes the agent do

An agent skill is a folder of instructions and templates that an AI coding agent loads when your request matches the skill. With live-dashboard loaded, the agent writes a single HTML file (index.html) containing a team dashboard. The page includes KPI cards, a 7-day sparkline, an activity feed and a linked-database style task table with status pills.

The page is designed to refresh. It can refresh on demand from a Refresh button, refreshes when it is opened, and can refresh automatically at an interval. A status pill in the top bar shows whether the data is live, syncing or stale.

  • Layout: the skill's references describe three layouts, and the agent picks one and states its choice.
  • Data source: a Notion connector when one is bound, otherwise built-in sample data so the page still displays.
  • Output: index.html, plus a connectors.json file when a real connector is used.

Install the live-dashboard skill

You can install the skill in either of two ways. Download the ZIP from the skill's page on this site and unzip it into one of the following locations, depending on whether you want it available everywhere or in one project.

Option A is your personal skills folder at ~/.claude/skills/. Option B is a project folder at .claude/skills/ inside your project. Option C is to upload the ZIP in the Claude apps under Settings → Capabilities → Skills.

  • Personal (all projects): unzip into ~/.claude/skills/ so the live-dashboard folder contains SKILL.md.
  • Single project: unzip into .claude/skills/ in that project's root.
  • Claude apps: upload the ZIP under Settings → Capabilities → Skills.

Ask for a dashboard with a natural request

You do not need a special command. The skill is triggered by requests that match its trigger phrases, such as 'team dashboard', 'notion dashboard', 'live dashboard', 'ops dashboard' and 'team workspace dashboard'. Name the team or workspace and say what numbers you want.

A good request states the workspace name, the KPIs and whether you want the page wired to Notion. The skill's own example asks for a Notion-style team dashboard for a named studio, with four KPIs and on-demand refresh.

  • Name the workspace, for example 'Acme Studio'.
  • List the KPIs you want, for example total tasks, done this week, active members and docs in review.
  • Say whether to connect Notion or to use sample data for a mockup.

Connect real data or use sample data

Without a connector the page uses seeded mock numbers so it displays without setup. These numbers are not real. The skill's description warns they can be mistaken for real figures, so label any screenshot or demo that uses them.

To show real data, the skill is designed to pull from Notion through a connector bound in the Open Design daemon. The skill's connector setting accepts notion, linear, stripe, posthog or mock. When a real connector is in use, the page sends a poll request to the daemon, and the daemon makes the provider call, so the page itself never handles provider URLs or tokens. If the poll fails, the page falls back to the seeded data and shows a small grey hint in the footer rather than an error banner.

  • Default connector is notion; mock forces sample data.
  • Connector setup involves Notion access, so check which workspace and permissions you grant.
  • The refresh interval defaults to 30 seconds and the stale threshold defaults to 90 seconds.
POST /api/od/connectors/poll with JSON body { project, read }

Check the page before sharing it

The skill includes a pre-emit checklist and a self-critique step, so the agent reports which checks it passed. Read that report before you rely on the page. Confirm that the status pill, the Refresh button and the footer source line match what you expect.

Freshness matters. If the pill shows Stale, the page has not refreshed successfully within the stale threshold, and the numbers may be old.

  • Confirm whether the footer shows a live source or sample data.
  • Press Refresh and watch the changed values and the new activity row.
  • Do not share previews that show Notion-linked data with people who should not see that workspace.

What people use it for

  • An internal ops or project status page for a small team, styled to look like Notion.
  • A client demo or set of screenshots of a Notion-like dashboard using sample data.
  • A starting HTML template with refresh and stale-state behaviour that a developer can adapt.
  • A quick mockup of KPI cards, a trend line and a task table to discuss layout with stakeholders.

Frequently asked questions

Is the live-dashboard agent skill free to use?

The skill is published under the Apache-2.0 licence, as listed on its page. Check the licence file in the source repository for the full terms before using it in a commercial product.

What do I need to run the live-dashboard skill?

You need a coding agent that can write files and make surgical edits. For real data you also need a Notion connector bound through the Open Design daemon. Without a connector, the skill uses built-in sample data.

Does the dashboard show real Notion data?

Only when a connector is bound. Without one, the page shows seeded mock numbers, which are not real and should not be used for production reporting.

How do I install the skill?

Download the ZIP and unzip it into ~/.claude/skills/ or a project's .claude/skills/ folder. Alternatively, upload the ZIP in the Claude apps under Settings, then Capabilities, then Skills.

Why does my dashboard show Stale?

The pill switches to Stale when no successful refresh has happened within the stale threshold, which defaults to 90 seconds. Press Refresh, or check the connector if real data is configured and the poll is failing.

Does the skill run scripts on my computer?

The skill is listed as not running scripts, but it does use the network. Its connector mode sends requests to the Open Design daemon, so review which workspace and permissions are granted.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

Use live-dashboard if you need a quick, Notion-styled status page for an internal team, a client demo, or a starting HTML template with refresh behaviour. Pick something else if you need production reporting based on real data without setting up and reviewing a connector, because the default sample numbers can be mistaken for real figures.

Download the skill