sync-health

Report health and readiness of LifeOS sync, vault, LLM, and service components.

20|4|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/nbramia/LifeOS --skill sync-health
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-health
Source: https://github.com/nbramia/LifeOS/tree/main/.claude/skills/sync-health
Command: npx skills add https://github.com/nbramia/LifeOS --skill sync-health

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Comprehensive health checkup for the LifeOS sync pipeline, vault indexing, LLM runtime, and services, surfacing stale, broken, or at-risk components to prevent outages.

Core Features & Use Cases

  • Collects latest run/status per source, orphan running rows, and top errors to surface failure patterns.
  • Evaluates vault index health (md files, BM25, and vector store population) and LLM runtime states (VRAM usage, active services) to warn before incidents.
  • Provides actionable guidance for remediation and readiness of nightly operations.

Quick Start

Run the sync-health check from the repository root to generate a structured health report for the LifeOS environment.

Frequently Asked Questions about sync-health

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

FAQPage Schema
How do I check LifeOS sync pipeline health and vault indexing status?

To check LifeOS sync pipeline health, run a diagnostic report that evaluates vault indexing for md files and BM25 population, identifies stale or broken components, and surfaces actionable remediation guidance to prevent outages.

What is the best way to monitor VRAM usage and LLM runtime states?

Monitoring VRAM usage and LLM runtime states involves environment introspection to evaluate active services and memory consumption, generating structured risk signals to warn you before incidents occur.

Why does my vector store population fail during nightly sync operations?

Vector store population fails during nightly sync operations due to orphan running rows or service failures. Collecting latest run status and top errors per source surfaces these failure patterns for targeted remediation.

Can I use deterministic checks to surface warnings for BM25 and Chroma population?

Yes, you can apply deterministic checks to evaluate BM25 and Chroma population readiness, using environment introspection to generate structured risk signals that guide operational remediation.

What limitations exist when diagnosing orphan running rows in a sync pipeline?

Diagnosing orphan running rows relies on collecting the latest run status per source, meaning limitations arise if environment introspection cannot access deterministic state data or structured risk signals are incomplete.