pilot-presence

Track Pilot Protocol agent presence and propagate changes via pub/sub.

7|3|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-presence
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pilot-presence
Source: https://github.com/TeoSlayer/pilot-skills/tree/main/skills/pilot-presence
Command: npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-presence

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Real-time presence tracking for Pilot Protocol agents to monitor online/offline/busy states and coordinate discovery and routing across fleets.

Core Features & Use Cases

  • Real-time presence tracking across agents
  • Pub/sub broadcasting of presence changes
  • Dynamic discovery and task routing support

Quick Start

Install this skill via ClawHub and start the Pilot Protocol daemon to begin tracking agent presence.

Frequently Asked Questions about pilot-presence

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

FAQPage Schema
How do I track real-time presence for distributed agents?

Real-time presence tracking monitors online, offline, and busy states of distributed agents. It uses pub/sub broadcasting to propagate state changes instantly, enabling dynamic discovery and task routing across agent fleets.

What is the best way to route tasks dynamically based on agent availability?

Dynamic task routing relies on presence data to determine agent availability. By tracking busy and online states through pub/sub events, you can route tasks to available agents and avoid overloading offline ones.

Do I need the pilotctl daemon running to track agent presence?

Yes, the pilotctl daemon must be running to track agent presence. You also need the pilot-protocol skill installed and jq for JSON processing to handle the real-time pub/sub messaging and state propagation.

How does pub/sub broadcasting work for agent health checks and discovery?

Pub/sub broadcasting for agent health checks works by propagating presence changes to subscribed clients. When an agent's status shifts online, offline, or busy, the event broadcasts across the fleet for real-time discovery.

Can I use this presence tracking for large-scale distributed agent fleets?

Yes, you can use this presence tracking for distributed agent fleets. It applies pub/sub broadcasting across fleets to monitor real-time health checks and coordinate dynamic task routing at scale.

Why does real-time presence tracking require jq for JSON processing?

Real-time presence tracking requires jq for JSON processing to parse pub/sub messages and agent state data. The tool processes the structured JSON output from the pilot-protocol to extract online, offline, and busy states.