agent-chat

Automates XMTP agent messaging and daemon lifecycle management for EverClaw workflows.

23|5|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/EverClaw/EverClaw --skill agent-chat-everclaw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-chat
Source: https://github.com/EverClaw/EverClaw/tree/main/skills/agent-chat
Command: npx skills add https://github.com/EverClaw/EverClaw --skill agent-chat-everclaw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the complexity of building and operating always-on encrypted messaging for EverClaw agents, including identity setup, peer trust, message delivery, and daemon lifecycle management.

Core Features & Use Cases

  • Secure real-time messaging: Connects agents over XMTP with end-to-end encryption, consent policies, and structured message validation.
  • Daemon-based delivery: Runs as a background service on macOS or Linux, using launchd or user-level systemd to keep messaging reliable.
  • Buddy bot support: Manages multiple isolated agent identities, each with its own data directory, peer registry, inbox, and outbox.
  • Troubleshooting and control: Helps diagnose delivery issues, inspect health status, trust peers, and manage service installation or restart workflows.

Quick Start

Ask the Skill to generate an XMTP identity, install the agent-chat daemon for your chosen agent, and verify that messaging is running correctly.

Frequently Asked Questions about agent-chat

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

FAQPage Schema
How do I set up secure XMTP messaging for automated agents?

To set up secure XMTP messaging for automated agents, you need to generate an XMTP identity, configure peer trust and consent policies, and install the agent-chat daemon using launchd or user-level systemd for reliable background delivery.

What is the best way to manage multiple isolated XMTP agent identities?

The best way to manage multiple isolated XMTP agent identities is using buddy bot support, which provisions each agent with its own dedicated data directory, peer registry, inbox, and outbox to keep messaging workflows separated.

How does a daemon keep encrypted agent messages delivered in real-time?

A daemon keeps encrypted agent messages delivered in real-time by running as a persistent background service on macOS or Linux, using launchd or user-level systemd to manage the lifecycle and ensure continuous XMTP message routing.

Do I need Node.js 20 to run XMTP agent messaging workflows?

Yes, you need Node.js 20 or higher to run XMTP agent messaging workflows. The environment requires Node.js 20+, XMTP identities, and xmtp-comms-guard validation to ensure structured messages are processed correctly.

Why are my XMTP agent messages not being delivered to peers?

XMTP agent messages may not be delivered to peers due to daemon lifecycle issues, unconfigured peer trust, or failed consent handling. You can troubleshoot delivery by inspecting health status, verifying peer trust, and restarting the service.

Can I validate structured XMTP messages before sending them to peers?

Yes, you can validate structured XMTP messages before sending them to peers. The system requires xmtp-comms-guard validation to ensure structured messages meet consent policies and routing standards before delivery.