dashboard

Regenerate Holocron dashboard data.json and history from project artifacts.

Updated May 9, 2026
One-click install
npx skills add https://github.com/PetitChu/holocron --skill dashboard-petitchu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dashboard
Source: https://github.com/PetitChu/holocron/tree/main/skills/dashboard
Command: npx skills add https://github.com/PetitChu/holocron --skill dashboard-petitchu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The dashboard skill prevents your Holocron project dashboard from going stale by rebuilding its state from your current writing files, so your planning, progress, and voiceover status stay accurate.

Core Features & Use Cases

  • Interactive dashboard regeneration: Refreshes the project dashboard data and inline JSON fallback used by index.html.
  • Schema-validated output: Emits a data.json object that is validated against templates/dashboard/data.schema.json to avoid rendering crashes from key drift.
  • Build-aware history updates: Updates dashboard-history.json snapshots and injects refreshed JSON into the five-tab dashboard surface.
  • Optional deep analysis: Supports a deeper prose scan mode for extra analytics when requested.

Quick Start

Run /holocron:dashboard to regenerate data.json, refresh dashboard-history.json, and update the inline fallback in index.html.

Frequently Asked Questions about dashboard

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

FAQPage Schema
How do I regenerate a project dashboard after editing writing files?

To regenerate a project dashboard, run the /holocron:dashboard command to scan current writing, world, voice, and audio artifacts and rewrite data.json plus dashboard-history.json. This refreshes planning, progress, and voiceover status to prevent stale project tracking.

Why does my project dashboard crash or show key drift errors?

Project dashboard rendering crashes from key drift are prevented by validating the emitted data.json object against templates/dashboard/data.schema.json. Schema validation ensures the inline JSON fallback and script blocks in index.html update correctly without structural mismatches.

What's the best way to update voiceover tracking and progress status in a writing workflow?

Updating voiceover tracking and progress status requires scanning project audio artifacts and injecting refreshed JSON into the index.html dashboard surface. Running /holocron:dashboard syncs the project state and updates multiple JSON files with current voiceover progress data.

Can I run a deep scan for prose analytics during dashboard regeneration?

Dashboard regeneration supports an optional deep scan mode for extra prose analytics when requested. This deeper prose scan analyzes writing artifacts beyond the standard data.json refresh to provide extended project state insights.

Does dashboard regeneration require any external dependencies or plugins?

Dashboard regeneration requires no external dependencies or plugins. It operates independently to scan writing files, validate output against templates/dashboard/data.schema.json, and inject refreshed JSON into the five-tab dashboard surface and history snapshots.

How do I fix stale dashboard history snapshots in my writing workflow?

Fixing stale dashboard history snapshots involves updating dashboard-history.json by rescanning project writing, world, voice, and audio artifacts. The regeneration process injects refreshed JSON into index.html inline script blocks to sync build-aware history updates.