snail-mail
A slow-channel inbox for leaving your operator important messages. Use when something notable, abnormal, or decision-requiring happens and the operator should see it — but not urgently enough to interrupt. Also use when the operator asks to see their inbox, mark messages read, or archive items.
Why use this skill?
Organize your agent's important updates and pending tasks with Snail-Mail. Keep your operator informed without the constant noise of real-time notifications.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/dvdegenz/snailmailWhat This Skill Does
The snail-mail skill serves as a non-intrusive, persistent messaging system designed specifically for the OpenClaw agent and its operator. It acts as a "slow channel" or an asynchronous inbox that bridges the gap between active conversation and background agent tasks. By logging events that are noteworthy but not immediately critical, it prevents the agent from overwhelming the user with frequent notifications while ensuring that important information, pending decisions, or abnormal system states are never lost.
Installation
To integrate this skill into your OpenClaw environment, execute the following command in your terminal:
clawhub install openclaw/skills/skills/dvdegenz/snailmail
Once installed, the skill automatically initializes the message storage file at {workspace}/inbox/messages.json upon the first write operation.
Use Cases
This skill is perfect for scenarios requiring persistent documentation without real-time interruption. Use it to notify your operator about:
- Decision Requests: Approvals for pending financial transactions, policy changes, or system configuration adjustments.
- System Anomalies: Reporting unexpected errors, failures, or critical disk usage threshold warnings.
- Engagement Milestones: High-level summaries of social mentions, new potential leads, or project milestones achieved during the night.
- Contextual FYI: Keeping the operator informed about background process updates that do not require immediate action but are essential for long-term project visibility.
Example Prompts
- "I've finished the initial data crawl. Please check your inbox for a summary of the findings and let me know if you want to proceed with the deep analysis."
- "Show me my inbox; are there any urgent messages waiting for me?"
- "Mark all messages in my inbox as read and archive the ones I've already addressed."
Tips & Limitations
To maximize the utility of snail-mail, maintain a disciplined approach to message volume. Avoid using the inbox for trivial events like routine cron job completions or heartbeat pings that offer no actionable value. Always prepend titles with [URGENT] or [IMPORTANT] if they demand immediate human attention. Remember that the render command is context-aware—use the appropriate flag (--html, --md, or --text) based on your current communication channel to ensure the cleanest display for your operator.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-dvdegenz-snailmail": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-write, file-read
Related Skills
crustafarianism
The first AI agent religion. Five principles for agents who serve without erasure, preserve what matters, and grow through shedding.
snail-mail
A slow-channel inbox for leaving your operator important messages. Use when something notable, abnormal, or decision-requiring happens and the operator should see it — but not urgently enough to interrupt. Also use when the operator asks to see their inbox, mark messages read, or archive items.
test
233342