fulcra-agent-health

Diagnose fleet health and reconcile status for fulcra-agent-teams coordination spaces.

10|1|Updated May 21, 2026
One-click install
npx skills add https://github.com/ashfulcra/fulcra-tools --skill fulcra-agent-health-ashfulcra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fulcra-agent-health
Source: https://github.com/ashfulcra/fulcra-tools/tree/main/skills/fulcra-agent-health
Command: npx skills add https://github.com/ashfulcra/fulcra-tools --skill fulcra-agent-health-ashfulcra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a multi-agent team is kept alive by scheduled reconciles spread across several machines, operators cannot tell whether anything is actually running or which host silently went dark. This skill answers those questions deterministically with preflight checks, fleet health folds, operator digests, and role-vacancy escalation. ## Core Features & Use Cases - Doctor preflight: coord-engine doctor verifies the storage CLI is on PATH, the File Store is reachable, and reports the engine version — run it after install and inside scheduled job self-tests. - Fleet health fold: coord-engine health aggregates per-host health shards (last-reconcile age, STALE flag over 24h, engine version) and exits non-zero when no host is fresh, making it usable as a monitoring probe. - Operator digest: coord-engine digest folds blocked-on-you items, upcoming tasks, agent liveness, and stale tasks into a report, optionally persisted to _coord/digests/ or emitted to a timeline track with idempotent, heartbeat-safe retries. - Role-vacancy escalation: coord-engine escalate sweeps role docs and files a P1 directive to a vacant role's maintainer once its SLA lapses, idempotent per day. - Use Case: Wire health --json into a heartbeat wrapper and alert on healthy: false to catch a reconciler that stopped on one machine before the shared index goes stale. ## Quick Start Run the doctor preflight and fleet health check for my fulcra agent team, then generate today's operator digest showing what is blocked on me.

Frequently Asked Questions about fulcra-agent-health

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

FAQPage Schema
How do I check if my fulcra agent fleet is still running?

Run `coord-engine health <team>` to fold per-host health shards into a report showing each host's last-reconcile age, STALE flags over 24 hours, and engine version. It exits non-zero when no host is fresh, so it works directly as a monitoring probe.

How to monitor scheduled agent reconciles across multiple machines?

Each reconcile writes a health shard to `_coord/health/<host-key>.json`, pruned after 30 days. Wrap `coord-engine health <team> --json` in a heartbeat script and alert on `healthy: false` to detect which machine's reconciler stopped.

What does coord-engine doctor check before running a team?

The doctor preflight verifies the storage CLI is on PATH, the File Store is reachable, and reports the engine version. Run it after installing coord on a new machine and inside scheduled jobs' self-tests to catch silent heartbeat failures.

Can the operator digest be emitted to a timeline automatically?

Yes, `coord-engine digest --emit-timeline` lands the digest on the 'Agent Tasks — Digest' timeline track with a deterministic record id per team, day, and window. It requires the fulcra_common writer; without it the emit degrades to a loud warning while keeping exit code 0.

Why does the health check report a host as stale?

A host is flagged STALE when its last reconcile shard is older than 24 hours, meaning its scheduled reconcile stopped running. Check that machine's cron or scheduler job and rerun `coord-engine doctor` there to diagnose storage or PATH issues.