/cu:dashboard

Launch the curaitor dashboard webapp locally with optional port and directory overrides.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jdidion/claude-plugins --skill cu-dashboard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: /cu:dashboard
Source: https://github.com/jdidion/claude-plugins/tree/main/plugins/curaitor/skills/cu%3Adashboard
Command: npx skills add https://github.com/jdidion/claude-plugins --skill cu-dashboard

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, npm, and includes scripts (resource) components.

What problem does it solve?

Launch the curaitor dashboard webapp locally, enabling a quick, browser-based interface for managing and inspecting the curaitor tool without extra setup.

Core Features & Use Cases

  • Start the hono/node-server webapp with a single launcher, handling self-guard logic to prevent nested servers.
  • Support optional port and directory overrides, and reuse an already-running server when available.
  • Provide clear readiness and logging behavior, with a printed URL for easy access.

Quick Start

Run the dashboard launcher script to start the curaitor dashboard.

Frequently Asked Questions about /cu:dashboard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I launch a local webapp dashboard with Node.js?

You can override the default port for the local startup by passing an optional port argument to the launcher script, which configures the Node.js webapp to listen on your specified port instead of the default.

Do I need npm and node installed to run the dashboard locally?

Yes, you need both Node.js and npm installed to run the dashboard locally, as the webapp relies on a Node.js-based server and its dependencies managed through npm to execute the launcher script.

What happens if I try to start the dashboard server when it is already running?

If the dashboard server is already running, the launcher script performs idempotent reuse of the existing server instead of starting a new one, utilizing self-guard checks to prevent nested servers from launching.

Can I specify a custom directory when starting the local webapp?

Yes, you can specify a custom directory during local startup by passing an optional directory override to the launcher script, allowing the Node.js webapp to operate within your designated folder path.

Why does the local dashboard launcher script take a long time to start?

The local dashboard launcher script includes a readiness wait of up to 30 seconds to ensure the Node.js webapp is fully initialized, logging activity to a local file before printing the URL for browser access.