skulk-mesh

Provide a REST API and message bus for inter-agent communication.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/Kitsune-Den/skulk-skills --skill skulk-mesh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skulk-mesh
Source: https://github.com/Kitsune-Den/skulk-skills/tree/main/skills/skulk-mesh
Command: npx skills add https://github.com/Kitsune-Den/skulk-skills --skill skulk-mesh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires express, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a lightweight, reliable inter-agent messaging bus that enables real-time communication, inbox management, and webhook-driven notifications across The Skulk.

Core Features & Use Cases

  • Intra-network messaging: send direct messages between known Skulk agents and broadcast to all.
  • Inbox and readouts: query agent inboxes to review received messages.
  • Webhook push delivery: register webhooks to receive instant message notifications for automation workflows.
  • Operational deployment: runs as a systemd service on Koda's Hearth and exposes a simple API for health checks and agent discovery.

Quick Start

Start the service locally and use the scripts/mesh.sh helper to send messages, register webhooks, and monitor health.

Frequently Asked Questions about skulk-mesh

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

FAQPage Schema
How do I set up inter-agent messaging for a REST API service?

Inter-agent messaging is enabled by deploying a lightweight REST API and message bus that allows known agents to send, read, and broadcast messages directly. The service handles input validation, error handling, and message persistence.

Can I use webhooks for real-time message push delivery to agents?

Webhooks can be registered to receive instant push notifications when messages arrive, enabling real-time automation workflows across agents without needing to continuously poll inboxes.

Does this messaging bus require express or systemd to operate?

The messaging bus relies on express for its REST API implementation and is designed for operational deployment as a systemd service. This ensures reliable health checks, agent discovery, and continuous uptime.

What is the best way to broadcast a message to all connected agents?

Broadcasting a message to all connected agents is achieved through a single REST API request to the messaging bus, which then distributes the message to every known agent's inbox in the network.

How do I retrieve and read messages from an agent's inbox?

Reading messages is done by querying an agent's specific inbox through the REST API, which returns all received messages stored in the simple data store for review.

Are there limitations to using a lightweight REST API for inter-agent communication?

Limitations include relying on a simple data store for persistence rather than a full database, meaning the REST API is optimized for lightweight inter-agent communication and inbox management rather than high-volume enterprise messaging.