fulcra-agent-automation

Schedule coord-engine heartbeats and install harness lifecycle hooks for unattended Fulcra agent teams.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? A Fulcra agent team's coordination views drift and sessions lose context unless someone manually runs reconcile and continuity commands; this Skill automates that upkeep so a team space stays healthy without human intervention. ## Core Features & Use Cases - Scheduled heartbeat: Installs a launchd (macOS) or cron (Linux) job that runs coord-engine reconcile, timeline projection, and digest emission on a fixed interval, with a self-test that fails loudly on broken PATH or auth. - Harness lifecycle adapters: Installs idempotent hooks for Claude Code, Codex, and OpenClaw that resume continuity on session start, park state before context loss, and read the bus v3 event queue on every wake. - Re-entrancy probes and migration: A probe table detects what is already installed, and re-running installers migrates coord2-era artifacts in place without duplicating jobs. - Use Case: An operator running a multi-agent team on a Mac installs the 20-minute heartbeat plus Claude Code hooks so the team's index stays healed, task transitions appear on the Fulcra timeline, and every session resumes structured continuity automatically. ## Quick Start Ask the agent to probe this host with the re-entrancy table and then install the heartbeat and the Claude Code adapter for your team and agent id, consenting before any scheduled job is created.

Frequently Asked Questions about fulcra-agent-automation

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

FAQPage Schema
How do I schedule coord-engine reconcile to run automatically?

Run scripts/install-heartbeat.sh with your team name and an optional interval in minutes (default 20). It creates a launchd LaunchAgent on macOS or a crontab line on Linux, and runs a self-test so a broken PATH or missing authentication fails loudly at install time.

How do I install Fulcra lifecycle hooks for Claude Code or Codex?

Use scripts/claude-code/install-claude-code.sh for Claude Code or scripts/codex/install_codex_watch.py for Codex, passing your team and agent id. Both write SessionStart and PreCompact hooks that resume continuity on wake and park state before context loss, and both are idempotent with an uninstall mode.

Does this skill still install a listener for incoming bus events?

No. The listener was retired with bus v3 and the listen verb was removed from the engine. Agents now read their event queue with coord-engine queue on every scheduled wake, and any surviving listener job should be stood down per the probe table.

What happens if I re-run an installer that is already installed?

Re-running is safe: every installer is idempotent and replaces its own job rather than duplicating it. Re-running also migrates coord2-era artifacts such as old hooks directories and automation ids to the current names with zero orphans.

Why does the heartbeat self-test fail even though reconcile works?

The chain emits timeline moments via digest --emit-timeline every tick, which requires the fulcra_common writer importable next to coord-engine. If that import fails, the timeline silently stays dark, so the installer exits with an error and instructions to reinstall with the writer.

Can I use this on Claude web or other cloud-only sessions?

Only as a best-effort prose practice. Cloud sessions have no persistent filesystem or scheduler, so you follow the lifecycle contract manually and use platform scheduled routines; durable background pickup requires a host-tier agent.