Register and manage AI agents via the Agent Coordinator HTTP API.
npx skills add https://github.com/mkalkere/agent-coordinator --skill ac-http
Please help me install this Agent Skill. Skill: ac-http Source: https://github.com/mkalkere/agent-coordinator/tree/main/.os/skills/coordination/ac-http Command: npx skills add https://github.com/mkalkere/agent-coordinator --skill ac-http
The Agent Coordinator HTTP API client enables programmatic access to the coordinator server, supporting agent registration, task claiming, release, completion, and heartbeat-based lifecycle management to coordinate work across multiple agents.
Configure the base_url for the Agent Coordinator and begin issuing ac_request calls to register agents and manage tasks.
High-intent search queries and answers about installing and using this skill.
To coordinate AI agents via HTTP API, use the Agent Coordinator client to register agents and claim tasks. This prevents duplicate work and ensures smooth handoffs by managing task completion, release, and deregistration.
Agent registration and health checks require HTTP endpoints like /agents, /tasks, and /health. These endpoints support agent lifecycle management, task claiming, and real-time system state observation.
Send heartbeats to monitor AI agent lifecycle and status by issuing HTTP requests through the Agent Coordinator client. This supports ongoing health checks and status updates to coordinate work across multiple agents.
Yes, you need a running Agent Coordinator server to manage task claiming and completion. The implementation requires a live server environment and uses tool.yaml to honor base_url, timeout, and retry configurations for HTTP calls.
Configure timeout and retry settings for HTTP agent coordination in tool.yaml. This file honors base_url configurations and ensures reliable HTTP calls for agent registration, task management, and health checks.
Using an HTTP API for task management prevents duplicate work and ensures smooth handoffs across multiple agents. It provides real-time coordination via endpoints like /agents and /tasks, unlike direct communication which lacks centralized state.
jcolanoCoordinate agent presence, notifications, tasks, and posts via authenticated loopColony API calls.
kinnerkarmanishLocks tasks atomically via filesystem-based mutexes for exclusive multi-agent processing.
zapabobOrchestrate multi-agent terminal processes with lifecycle management and conflict prevention.
yashvinthanImplement Python background jobs with Celery and Redis.
