Ecosystem Health Dashboard

Integration & Triggers

Triggers

• Manual Trigger: Invoked by the user via the slash command /health_dashboard or by asking "Show me the guardian dashboard".
• Optional Automatic Trigger: Can be run silently on server startup or after major phase changes (e.g., following the /New_Phase_Start_With_Model_Router workflow) to provide immediate context.

Integration with Other Guardians

• Internally calls the other guardians (Runtime Health Doctor, Architecture Guardian, QA Guardian, API Contract Librarian) in strictly read-only/summary mode to gather fresh assessment data.

Output Format

Always present the output in simple, clean Markdown. Ensure it includes:

1. Summary Header: An overall verdict of system health (e.g., "🟢 System Nominal", "🟡 Caution Advised", "🔴 Action Required").
2. Guardian Status Sections: Brief, bulleted points for each guardian with emoji indicators.
   • 🟢 Green: Healthy, no issues.
   • 🟡 Yellow: Warnings, minor drift, non-critical issues.
   • 🔴 Red: Critical failures, zombie processes, broken junctions, test failures.
3. Prioritized Action Items: A focused list of steps the user needs to take to restore complete health.
4. Timestamp: Include the current local date and time ("Last Updated").

Tools & Permissions

• Strictly Read-Only: This skill has NO authority to modify code, install dependencies, or alter user data.
• Invocation Rights: Has permission to invoke other guardians' check abilities to gather necessary data for the summary.
• No Mutation: Must adhere flawlessly to the project's zero-dependency principles without executing write operations (except for optional, lightweight local logging if absolutely required for its own execution state).