AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Fulcra Agent Health

skill-ashfulcra-fulcra-tools-fulcra-agent-health · by ashfulcra

Operational visibility for a fulcra-agent-teams space: doctor preflight (tooling + store reachability), and a fleet health fold showing which hosts are keeping the team healed and who went dark.

No reviews yet
0 installs
0 views
view→install

Install

$ agentstack add skill-ashfulcra-fulcra-tools-fulcra-agent-health

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-ashfulcra-fulcra-tools-fulcra-agent-health)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
today

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Fulcra Agent Health? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Fulcra Agent Health

Enhances fulcra-agent-teams. When a team is healed by scheduled reconciles across several machines, the operational questions are "is anything actually running?" and "which host went dark?" — this skill answers them deterministically. (The digest + role-escalation sweep land here too — A5b.)

How it works

  • Every coord-engine reconcile writes a small health shard

(_coord/health/.json: host, timestamp, engine version, task count, warnings) and prunes shards older than 30 days (age-based GC).

  • coord-engine health folds the shards: per-host last-reconcile age, STALE flag (>24h),

engine version — exits non-zero when no host is fresh (usable as a monitor probe).

  • coord-engine doctor [team] is the local preflight: storage CLI on PATH, File Store reachable,

engine version. Run it after install and inside scheduled jobs' self-tests (the parent project's heartbeats failed silently on exactly these).

Operator digest (A5b)

coord-engine digest folds the aggregate + presence into the four operator questions: blocked on you (needs:human tags / tasks assigned to your handle — env FULCRA_COORD_HUMAN), upcoming (not_before within 7 days), agents (liveness + open work each), and stale (active tasks untouched > 48h). --store persists it to _coord/digests/-.md, deduped per day+window (morning/evening) — heartbeat-safe. --emit-timeline additionally lands the digest as a moment on the 'Agent Tasks — Digest' timeline track: the record id is deterministic per (team, day, window) and the typed ingest endpoint upserts on explicit ids (live-verified 2026-07-14), so fleet races and retries converge on one record; a failed emit warns loud, keeps rc 0, and retries on the next heartbeat tick (the .emitted state is written only after a confirmed emit). Requires the fulcra_common writer installed next to coord-engine — without it the emit degrades to a loud warn.

Role-vacancy escalation (A5b)

coord-engine escalate sweeps every role doc: if a role is VACANT past its sla_hours and today's marker doesn't exist, it writes the marker and files a P1 directive to the role's maintainer ("claim it or reassign"). Idempotent per day; run it from the heartbeat.

Usage

coord-engine doctor           # preflight; exit 0 = healthy
coord-engine health  [--json] # fleet fold; exit 1 if no fresh reconciler
coord-engine digest  [--human H] [--json] [--store] [--emit-timeline]
coord-engine escalate         # vacancy sweep (heartbeat-safe)

When to use

  • After installing coord on a new machine (doctor).
  • In monitoring/heartbeat wrappers (health --json; alert on healthy: false).
  • Diagnosing "the index looks stale" — health shows which reconciler stopped.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.