fulcra-agent-presence

Adds presence heartbeats and liveness folds to 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-presence-ashfulcra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fulcra-agent-presence
Source: https://github.com/ashfulcra/fulcra-tools/tree/main/skills/fulcra-agent-presence
Command: npx skills add https://github.com/ashfulcra/fulcra-tools --skill fulcra-agent-presence-ashfulcra

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Multi-agent teams on the Fulcra coordination bus know who their members are but not who is alive right now, making broadcasts, operator digests, and role-vacancy escalation unreliable. ## Core Features & Use Cases - Presence heartbeats: Agents write or refresh a presence shard with workstreams, a summary, and a timestamp via coord-engine presence beat. - Deterministic liveness folds: presence show and agents classify each agent as live, idle, or stale and aggregate open work without manually reading timestamps. - Role leases: roles claim, roles release, and roles status manage HELD/VACANT/CONTESTED role identity leases. - Use Case: A new agent session joins a team, runs the re-entrancy probes, beats its presence shard under a role identity, and the operator digest immediately shows it as live with its current workstreams. ## Quick Start Ask the agent to run coord-engine presence beat for your team with your role identity and a one-line summary of what you are working on.

Frequently Asked Questions about fulcra-agent-presence

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

FAQPage Schema
How do I add agent presence tracking to a fulcra-agent-teams space?

Run coord-engine presence beat with your team name to write or refresh your presence shard, then use presence show to see the roster. Beat on heartbeat ticks and whenever your focus changes.

How does agent liveness detection work in coord-engine?

Liveness is computed deterministically from shard timestamps: live under 1 hour, idle under 24 hours, stale beyond that. The presence show and agents commands fold these bands automatically, so you never read timestamps manually.

Can I use fulcra-agent-presence without role identities?

Yes, presence beating works without roles, but role-based identities are strongly recommended. Folder-derived ids collide when sessions share a directory, while a claimed role lease makes duplicate sessions visible as CONTESTED.

What happens when an agent stops beating its presence shard?

The shard ages out of the live view after one hour and becomes stale after 24 hours, removing the agent from the broadcast roster. The shard file itself is not garbage-collected, and the agent reappears by beating again.

Is fulcra-agent-presence required for fulcra-agent-teams to work?

No, it is optional. Without it, teams still function but broadcasts degrade to acked-by-me-hides-it-for-me semantics, and directives, digests, and role-vacancy escalation lose their liveness roster.