Snail Mail - Operator Inbox for Openclaw

A slow-channel communication bridge that allows AI agents to leave non-urgent messages and decision requests for their human operators.

dvdegenz
v1.0.0
Feb 13, 2026
0
1.9k
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install snailmail

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install snailmail using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Snail Mail - Operator Inbox?

Snail Mail is a specialized communication tool designed for Openclaw Skills that provides a buffer between an AI agent and its operator. Instead of interrupting the operator with every minor event or non-critical update, this skill captures important information and presents it in a structured inbox format when the operator is ready to review it.

By leveraging this skill, developers can implement a asynchronous workflow where agents log notable events, security patterns, or policy questions that require human oversight. This ensures that the human operator remains informed of high-value context without the fatigue of constant, trivial notifications.

Snail Mail - Operator Inbox Use Cases

  • Capturing events that require human decisions, such as payment approvals or policy resolutions.
  • Documenting abnormal patterns like security events or system failures that aren't immediate emergencies.
  • Archiving interesting milestones or media mentions for later review.
  • Providing FYI context that might be useful for future debugging or project planning.

How Snail Mail - Operator Inbox Works

  1. The AI agent identifies a notable event that does not require an immediate interruption.
  2. The agent uses the CLI tool to add a message to the inbox, specifying priority and a scannable title.
  3. Messages are persisted locally in a structured JSON file within the workspace using atomic rename writes to prevent corruption.
  4. During periodic heartbeats or upon manual request, the agent checks for unread items.
  5. The operator requests an inbox check, prompting the agent to render the messages in the appropriate format (HTML, Markdown, or Plain Text) for the current communication channel.

Snail Mail - Operator Inbox Setup

The inbox is automatically initialized upon first use. Ensure you have the skill integrated into your workspace environment.

# The inbox file is created at {workspace}/inbox/messages.json on first use.
# To add a message manually:
node {skill}/scripts/inbox.js add "Title" "Description of what happened"

Snail Mail - Operator Inbox Data Schema & Taxonomy

The skill maintains a flat-file database to ensure simplicity and portability within Openclaw Skills environments. The data is structured as follows:

Property Description
id Unique identifier for each message entry
title A short, scannable summary including the who or what
message 1-3 sentences of context including relevant links
priority Classified as urgent, important, or normal
status Current state of the message: unread, read, or archived
timestamp The date and time the entry was created

Snail Mail - Operator Inbox Advanced Features

  • Automated channel detection to render messages in HTML for web/Telegram or Markdown for Slack/Discord.
  • Atomic rename writes (writing to .tmp then renaming) to ensure data integrity during agent operations.
  • Proactive heartbeat integration that only surfaces urgent or important items while keeping normal messages silent.
  • Comprehensive archival system to keep the active inbox focused on current actionable items.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*