bridge-health

Aggregate liveness probes and telemetry to assess bridge daemon fleet health.

10|1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/mishahanin/heading-os --skill bridge-health
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bridge-health
Source: https://github.com/mishahanin/heading-os/tree/main/.claude/skills/bridge-health
Command: npx skills add https://github.com/mishahanin/heading-os --skill bridge-health

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill resolves uncertainty regarding system status by providing a centralized, read-only health check for the bridge daemon fleet, identifying crashes, version drift, and configuration issues before they impact operations.

Core Features & Use Cases

  • Fleet Health Grid: Displays a status overview of all workspaces, including heartbeat freshness, versioning, and active sessions.
  • Adoption Gate Verification: Summarizes key telemetry metrics to determine if the system is ready to scale from Phase 1 to Phase 2.
  • Use Case: When the dashboard sync-pill turns red or amber, use this tool to instantly diagnose whether the local daemon is down, misconfigured, or experiencing version drift across the executive fleet.

Quick Start

Run the bridge-health skill to perform a full fleet diagnostic check including the adoption gate metrics.

Frequently Asked Questions about bridge-health

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

FAQPage Schema
How do I run a health check on a bridge daemon fleet?

To perform a bridge daemon fleet health check, execute the automated CLI script to aggregate local liveness probes and remote telemetry data, validating daemon uptime, version parity, and adoption gate metrics.

What is the best way to monitor daemon uptime and version drift in real-time?

Real-time daemon monitoring aggregates heartbeat freshness, active session data, and versioning telemetry into a centralized fleet health grid, instantly identifying crashes and version drift before they impact operations.

How does adoption gate verification work for bridge daemon telemetry?

Adoption gate verification summarizes key bridge daemon telemetry metrics to determine if the system meets stability and configuration consistency requirements, confirming readiness to scale from Phase 1 to Phase 2.

Why does my dashboard sync-pill turn red or amber during bridge daemon operations?

A red or amber dashboard sync-pill indicates bridge daemon instability, meaning the local daemon is down, misconfigured, or experiencing version drift across the executive fleet that requires immediate diagnostic attention.

Does this health monitoring tool require special dependencies to validate executive workspaces?

No special dependencies are required; the health monitoring operates through automated CLI script execution to validate synchronization between CEO and executive workspaces, ensuring system stability and configuration consistency.

Can I diagnose configuration issues across a bridge daemon fleet without modifying the system?

Yes, you can run a centralized, read-only health assessment to safely diagnose configuration issues, crashes, and version parity across the bridge daemon fleet without impacting active operational environments.