fusebase-flow-health-check

Diagnose Fusebase Flow installation health by ownership layer with verdict codes.

6|Updated May 29, 2026
One-click install
npx skills add https://github.com/fusebase-dev/fusebase-flow --skill fusebase-flow-health-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fusebase-flow-health-check
Source: https://github.com/fusebase-dev/fusebase-flow/tree/main/flow-skills/fusebase-flow-health-check
Command: npx skills add https://github.com/fusebase-dev/fusebase-flow --skill fusebase-flow-health-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the time-consuming, error-prone manual process of debugging broken Fusebase Flow installations after updates, configuration changes, or CLI updates, which often requires deep knowledge of layer ownership to diagnose correctly.

Core Features & Use Cases

  • Layer-specific drift diagnosis: Automatically identifies the exact ownership layer of issues (CLI-owned, Flow-owned, shared merge, active exceptions, or critical breakage) with clear, standardized verdicts.
  • Advisory conflict reporting: Surfaces non-critical issues like stale CLI snapshots or custom skill blocks at risk without triggering false positive failure states.
  • Guided recovery workflows: Only offers Flow-owned recovery when appropriate, and directs operators to fix CLI-owned drift first via the FuseBase CLI to avoid redundant or conflicting fixes.
  • Use Case: After running a fusebase update that breaks your Flow agent loading, run this health check to immediately determine if the issue is a CLI layer drift (fix via CLI refresh) or a Flow layer drift (run recovery with one confirmation).

Quick Start

Request a Fusebase Flow health check to receive an immediate verdict on your installation's status and clear, actionable next steps.

Frequently Asked Questions about fusebase-flow-health-check

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

FAQPage Schema
How do I diagnose Fusebase Flow agent loading failures after an update?

Run a Fusebase Flow health check to diagnose agent loading failures. It separates issues by ownership layer, providing standardized verdict codes to identify whether CLI or Flow layer drift caused the breakage.

What is layer drift in Fusebase Flow and how do I identify it?

Layer drift occurs when CLI-owned or Flow-owned assets become inconsistent after updates. A health check identifies drift by categorizing failures into ownership layers with clear, standardized verdicts and advisory conflict reporting.

How do I resolve conflicts between FuseBase CLI and Flow-owned agent assets?

Resolve CLI and Flow asset conflicts by following guided recovery workflows. The health check directs operators to fix CLI-owned drift first via the CLI, then offers Flow-owned recovery to avoid redundant fixes.

Does the Fusebase Flow health check modify my installation during diagnosis?

The Fusebase Flow health check does not modify your installation during diagnosis. It executes as a read-only, bounded diagnostic process that provides advisory conflict reporting and clear verdict codes.

Why does my Fusebase Flow installation show stale CLI snapshot warnings?

Stale CLI snapshot warnings appear during a health check as advisory conflict reporting. They surface non-critical issues at risk without triggering false positive failure states, indicating a need for a CLI refresh.

Can I use this health check for post-update verification of Fusebase Flow?

You can use this health check for post-update verification of Fusebase Flow. It eliminates manual troubleshooting by immediately determining if update issues stem from CLI layer drift or Flow layer drift.