dashboard

Included with Lifetime

$97 forever

Generate and open the harness run dashboard. Reads .harness/*.json state files, builds a self-contained HTML file, and opens it in the browser. Use when the user asks to see the dashboard, check run status, or view experiment history. For live monitoring during a run, suggest /loop 30s /harness:dashboard.

Web Dev

What this skill does


# Harness: Dashboard

Generate a self-contained HTML dashboard from `.harness/` state files and open it in the browser.

## Step 1: Locate the harness directory

```bash
if [ -d ".harness" ]; then
  HARNESS_DIR=".harness"
elif [ -d "../.harness" ]; then
  HARNESS_DIR="../.harness"
else
  echo "NO_HARNESS_DIR"
fi
echo "Using: $HARNESS_DIR"
```

If no `.harness/` directory exists, tell the user no runs have been recorded yet and stop.

## Step 2: Generate the dashboard

```bash
node "${CLAUDE_PLUGIN_ROOT}/scripts/render-dashboard.js" "$HARNESS_DIR"
```

The script writes `$HARNESS_DIR/dashboard.html` and prints a text summary. Capture and show the summary.

## Step 3: Open in browser

```bash
open "${HARNESS_DIR}/dashboard.html" 2>/dev/null \
  || xdg-open "${HARNESS_DIR}/dashboard.html" 2>/dev/null \
  || echo "Open ${HARNESS_DIR}/dashboard.html in your browser"
```

## Step 4: Report to the user

Tell the user:
- The dashboard was opened (or give the path to open manually)
- The text summary from Step 2 (workflow status, phase counts)
- If any phase is `failed`, highlight it

## Live monitoring

If the user wants the dashboard to refresh automatically while a run is in progress:

> Run `/loop 30s /harness:dashboard` to refresh every 30 seconds.

Files: 1

Size: 1.6 KB

Complexity: 12/100

Category: Web Dev

Source: https://github.com/flight505/flight505-marketplace/tree/main/harness/skills/dashboard

Related in Web Dev

generating-lwc-components

Included

Lightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use generating-apex), Aura components, or Visualforce.

Web Devscripts

tanstack-query

Included

Manage server state in React with TanStack Query v5. Set up queries with useQuery, mutations with useMutation, configure QueryClient caching strategies, implement optimistic updates, and handle infinite scroll with useInfiniteQuery. Use when: setting up data fetching in React projects, migrating from v4 to v5, or fixing object syntax required errors, query callbacks removed issues, cacheTime renamed to gcTime, isPending vs isLoading confusion, keepPreviousData removed problems.

Web Devscripts

document-processor-api

Included

Process documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.

Web Devscripts

nutrient-document-processing

Included

Web Devscripts

tanstack-query

Included

Manage server state in React with TanStack Query v5. Covers useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions. Use when setting up data fetching, fixing v4→v5 migration errors (object syntax, gcTime, isPending, keepPreviousData), or debugging SSR/hydration issues with streaming server components.

Web Devscripts

accelint-nextjs-best-practices

Included

Next.js performance optimization and best practices. Use when writing Next.js code (App Router or Pages Router); implementing Server Components, Server Actions, or API routes; optimizing RSC serialization, data fetching, or server-side rendering; reviewing Next.js code for performance issues; fixing authentication in Server Actions; or implementing Suspense boundaries, parallel data fetching, or request deduplication.

Web Devscripts