hoard-sending-stone

Send and receive messages between Pi sessions via a local HTTP/SSE bus.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/dotBeeps/hoard --skill hoard-sending-stone
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hoard-sending-stone
Source: https://github.com/dotBeeps/hoard/tree/main/morsels/skills/hoard-sending-stone
Command: npx skills add https://github.com/dotBeeps/hoard --skill hoard-sending-stone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Send and receive messages between Pi sessions using a local HTTP/SSE bus for cross-agent coordination and help requests. The sending stone enables allies to report results, check in, and synchronize actions across multiple sessions on a single host.

Core Features & Use Cases

  • Cross-session messaging via an HTTP server and SSE stream for bidirectional communication.
  • Enables help requests, progress updates, and result reporting between a primary agent and allied sessions.
  • Real-world scenario: coordinate a task across tools running in separate sessions and share findings instantly.

Quick Start

Start the local hoard sending stone service and connect an ally session to begin cross-agent messaging.

Frequently Asked Questions about hoard-sending-stone

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

FAQPage Schema
How do I send and receive messages between local agent sessions using HTTP and SSE?

Cross-agent coordination between local sessions uses an HTTP server and SSE stream to support bidirectional messaging, allowing a primary agent and allied sessions to send and receive messages on a single host.

What environment variables do I need to route messages to ally sessions on a local host?

Routing messages to allied sessions requires setting the HOARD_STONE_PORT and HOARD_ALLY_DEFNAME environment variables to ensure the local HTTP/SSE bus correctly directs help requests and result reporting.

Can I coordinate multiple Pi sessions running on the same host for a shared task?

Yes, coordinating multiple Pi sessions on a single host is supported via the local HTTP/SSE bus, enabling allied sessions to check in, report results, and synchronize actions instantly across separate tools.

What is the best way to report progress updates from an ally session back to a primary agent?

Reporting progress updates from an ally session to a primary agent is handled via the local HTTP/SSE bus, which streams real-time messages and results across sessions operating on the same host.

Does cross-agent messaging with a local HTTP server require external network access?

Cross-agent messaging via the local HTTP server and SSE stream operates entirely on a single host. It routes messages using specific environment variables and does not require external network access to coordinate sessions.