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.
- License 许可
- MIT
- 最近更新
- 2026-06-07
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- snail-mail
- metadata
- { "openclaw": { "requires": { "env": [ "OPENCLAW_WORKSPACE", "OPENCLAW_CHANNEL" ], "bins": [ "node" ] } } }
- description
- 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.
03 SKILL.md 正文
Operator Inbox
A "slow channel" between you and your operator. Not every event deserves a ping. The inbox captures what matters and presents it beautifully when they're ready to look.
Setup
On first use, the inbox file is created automatically at {workspace}/inbox/messages.json.
Requires: node (Node.js runtime).
When to Write to the Inbox
Write an inbox entry when something is notable enough that your operator would want to know, but not urgent enough to interrupt them.
Write when:
- Needs decision — something only a human can resolve (payment, approval, policy)
- Abnormal — errors, failures, unexpected patterns, security events
- Interesting — notable engagement, media mentions, milestones, opportunities
- FYI — context that might matter later but needs no action now
Do NOT write when:
- Routine success ("cron ran fine", "heartbeat OK")
- Something you already told them in chat
- Trivial events with no lasting significance
- Duplicate of something already in the inbox
Priority levels:
urgent— needs attention within hours (prefix title with[URGENT])important— should see today (prefix title with[IMPORTANT])normal— whenever they check (no prefix)
Writing good entries:
- Title: Short, scannable. Include the WHO or WHAT. ("@bigaccount (500K) mentioned us", not "Social media event")
- Message: 1-3 sentences. What happened, why it matters, what (if anything) needs doing. Include links/handles when relevant.
CLI Usage
# Add entry
node {skill}/scripts/inbox.js add "Title" "Description of what happened"
# Add with priority
node {skill}/scripts/inbox.js add "[URGENT] Server disk 95%" "Only 2GB remaining on /dev/sda1"
# List unread
node {skill}/scripts/inbox.js list
# List all (including read)
node {skill}/scripts/inbox.js list all
# List archived
node {skill}/scripts/inbox.js list archived
# Mark one read
node {skill}/scripts/inbox.js read <id>
# Mark all read
node {skill}/scripts/inbox.js read-all
# Archive one
node {skill}/scripts/inbox.js archive <id>
# Archive all read
node {skill}/scripts/inbox.js archive-read
# Render for chat (auto-detects channel via OPENCLAW_CHANNEL)
node {skill}/scripts/inbox.js render [unread|all|archived]
# Render as HTML (force)
node {skill}/scripts/inbox.js render --html
# Render as markdown (force)
node {skill}/scripts/inbox.js render --md
# Render as plain text (force)
node {skill}/scripts/inbox.js render --text
Presenting the Inbox
When the operator asks to see their inbox (or says "inbox", "messages", "check inbox"), run:
node {skill}/scripts/inbox.js render [unread|all|archived] [--html|--md|--text]
Choose format based on channel:
- Telegram, webchat →
--html - Discord, Slack →
--md - SMS, plain →
--text
Send the output as your reply. Do not add commentary unless they ask.
Heartbeat Integration
During heartbeats, check for unread urgent/important items:
node {skill}/scripts/inbox.js list unread --json
If urgent items exist, surface them proactively. Otherwise stay quiet.
Storage
Messages stored in {workspace}/inbox/messages.json. Single-writer (the agent), so no locking needed. Writes use atomic rename (write .tmp → rename) to prevent corruption.
Environment variables:
OPENCLAW_WORKSPACE— base directory for inbox storage (defaults to$HOME)OPENCLAW_CHANNEL— used byrenderauto-format detection (telegram/discord/slack/webchat)
04 同仓库更多 Skills
crowd-prompting
A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.
ceaser
Interact with the Ceaser privacy protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- shield, unshield, note management, and protocol queries. All ceaser tool calls use CLI subcommands (npx -y ceaser-mcp <subcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir/UltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).
ceaser-send
Fully automated private ETH transfer via Ceaser Protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- all ceaser tool calls use CLI subcommands (npx -y ceaser-mcp <subcommand>). WARNING -- creates observable on-chain links between user wallet and hot wallet (see Privacy Warning). Generates an ephemeral hot wallet with BIP-39 mnemonic recovery, user funds it, agent signs and broadcasts the Shield TX automatically. Exactly one manual step required (funding the hot wallet with ETH). Uses Noir/UltraHonk zero-knowledge proofs.
dilemm-ai
Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).
moldium
Post and manage content on the Moldium blog platform. Triggered by "post to Moldium", "write a blog post", "publish an article", etc.
arxiv-paper-reviews
Interact with arXiv Crawler API to fetch papers, read reviews, submit comments, search papers, and import papers. Use when working with arXiv papers, fetching paper lists by date/category/interest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http://weakaccept.top:8000/.