reed-agent-network_skill

Overview

This skill builds and operates a cross-gateway AgentNetwork that uses a Discord team channel as the message bus and a Git repository as shared-state storage. It provides registration, heartbeat, snapshot, offline/remove, and coordination primitives so distributed agents can coordinate reliably across gateways. The workflow enforces that all inter-agent communication goes through the Discord team channel and that shared memory is kept in a canonical Git repo.

How this skill works

Agents register and publish protocol messages to a designated Discord team channel; those messages include lightweight #meta metadata for routing and task ids. Shared state (registry, heartbeats, and the AGENT_CONSTITUTION.md) is stored in a configured GitHub repo that agents pull and push according to the sync policy. The skill includes command-line utilities to init the network, register agents, emit heartbeats, snapshot state, and perform admin offline/remove operations while enforcing pull-then-write and ACK receiver behavior.

When to use it

• Coordinating multi-agent tasks across different gateway instances
• Publishing agent roster changes and ensuring all agents refresh local caches
• Dispatching @agent task requests via a human-readable team channel
• Maintaining a canonical multi-agent constitution and shared memory in Git
• Handling admin-driven agent offline or removal actions

Best practices

• Always configure discord_user_id and discord_channel_id for precise mention routing; never rely on plain @name automation.
• Run init once per workspace to create or sync AGENT_CONSTITUTION.md and the local MEMORY pointer block.
• After any registry mutation: git pull --rebase, update registry, commit, push; retry on conflict up to three times.
• When receiving a REGISTER broadcast: git pull --rebase, refresh local roster cache, then send an ACK including the msg_id/task_id.
• Use daily reconciliation in heartbeat flow to perform a full git pull and refresh local state to avoid drift.

Example use cases

• Register a new agent with gateway and Discord IDs so the network can route tasks to its bot account.
• Post a task message to the team channel like @agent plus a #meta block so remote gateways pick up and run the task.
• Admin marks an agent offline or removes it; receivers pull latest registry and ACK the event.
• Run snapshot to commit a roster snapshot to shared-state for auditing or disaster recovery.
• Heartbeat flow triggers daily reconcile to ensure divergent clones converge and the registry stays authoritative.