Helios - Dashboard Auditor

Detect and report drift between dashboard data and agent state files.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/chadyi-king/mission-control-workspace --skill helios-dashboard-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Helios - Dashboard Auditor
Source: https://github.com/chadyi-king/mission-control-workspace/tree/main/agents/helios
Command: npx skills add https://github.com/chadyi-king/mission-control-workspace --skill helios-dashboard-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helios detects and reports drift between the mission-control dashboard data and the state of all agents, ensuring the truth on the dashboard matches reality across the ecosystem.

Core Features & Use Cases

  • Data integrity checks across data sources (mission-control-dashboard/data.json, agents/AGENT_STATE.json, current-task.md, MEMORY.md, ACTIVE.md) to surface timestamp drift, missing tasks, and misaligned statuses.
  • Cross-source consistency verification with automated alerts to CHAD_YI when discrepancies are found, plus safe auto-fixes where appropriate.
  • Real-world scenarios include reconciling outdated ACTIVE.md views with data.json, validating task assignments, and generating structured audit reports for governance and accountability.

Quick Start

Run Helios to perform automated 15-minute dashboard audits and report findings to CHAD_YI.

Frequently Asked Questions about Helios - Dashboard Auditor

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

FAQPage Schema
How do I audit dashboard data integrity across agent state files?

You can audit dashboard data integrity by running automated checks across data.json, ACTIVE.md, current-task.md, MEMORY.md, and agent state files to surface timestamp drift, missing tasks, and misaligned statuses between sources.

What causes dashboard data drift between ACTIVE.md and data.json?

Dashboard data drift occurs when mission-control dashboard data.json becomes out of sync with agent state files and ACTIVE.md views, causing misaligned statuses and outdated task assignments that require cross-source consistency verification.

Can I automatically fix discrepancies between agent state files and dashboard data?

Yes, you can apply optional safe auto-fixes to resolve discrepancies found during dashboard audits, while structured audit reports and automated alerts to CHAD_YI ensure governance and accountability for any changes made.

How often should I run dashboard audits to prevent data inconsistencies?

Dashboard audits should run at automated 15-minute intervals to detect and report drift between mission-control dashboard data and the state of all agents, ensuring the truth on the dashboard matches reality across the ecosystem.

Does the dashboard auditor validate task assignments across current-task.md and MEMORY.md?

Yes, the dashboard auditor validates task assignments by applying data integrity checks across current-task.md, MEMORY.md, and agent state files to surface missing tasks and timestamp drift, triggering alerts when inconsistencies are found.

What is cross-source consistency verification for mission-control dashboards?

Cross-source consistency verification is the process of comparing mission-control dashboard data against multiple agent state files and markdown records to detect status misalignment, timestamp drift, and missing task entries.