[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75FN4N6P26KBH4TX0TYRDEQ":3,"skill-same:01M75FN4N6P26KBH4TX0TYRDEQ":55},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":38,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M75FN4N6P26KBH4TX0TYRDEQ","snail-mail",null,"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.","javimosch\u002Fopen-claw-skills","javimosch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12900508?v=4","01M6D3F2AS6PV75ET9PZ1QGP8J","Javier Leandro Arancibia","01M75B8NCTAJG9WH5YNZH7C3D8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdvdegenz\u002Fsnail-mail\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: snail-mail\ndescription: 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.\nmetadata: {\"openclaw\": {\"requires\": {\"bins\": [\"node\"], \"env\": [\"OPENCLAW_WORKSPACE\", \"OPENCLAW_CHANNEL\"]}}}\n---\n\n# Operator Inbox\n\nA \"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.\n\n## Setup\n\nOn first use, the inbox file is created automatically at `{workspace}\u002Finbox\u002Fmessages.json`.\n\nRequires: `node` (Node.js runtime).\n\n## When to Write to the Inbox\n\nWrite an inbox entry when something is **notable enough that your operator would want to know, but not urgent enough to interrupt them.**\n\n### Write when:\n- **Needs decision** — something only a human can resolve (payment, approval, policy)\n- **Abnormal** — errors, failures, unexpected patterns, security events\n- **Interesting** — notable engagement, media mentions, milestones, opportunities\n- **FYI** — context that might matter later but needs no action now\n\n### Do NOT write when:\n- Routine success (\"cron ran fine\", \"heartbeat OK\")\n- Something you already told them in chat\n- Trivial events with no lasting significance\n- Duplicate of something already in the inbox\n\n### Priority levels:\n- `urgent` — needs attention within hours (prefix title with `[URGENT]`)\n- `important` — should see today (prefix title with `[IMPORTANT]`)\n- `normal` — whenever they check (no prefix)\n\n### Writing good entries:\n- **Title:** Short, scannable. Include the WHO or WHAT. (\"@bigaccount (500K) mentioned us\", not \"Social media event\")\n- **Message:** 1-3 sentences. What happened, why it matters, what (if anything) needs doing. Include links\u002Fhandles when relevant.\n\n## CLI Usage\n\n```bash\n# Add entry\nnode {skill}\u002Fscripts\u002Finbox.js add \"Title\" \"Description of what happened\"\n\n# Add with priority\nnode {skill}\u002Fscripts\u002Finbox.js add \"[URGENT] Server disk 95%\" \"Only 2GB remaining on \u002Fdev\u002Fsda1\"\n\n# List unread\nnode {skill}\u002Fscripts\u002Finbox.js list\n\n# List all (including read)\nnode {skill}\u002Fscripts\u002Finbox.js list all\n\n# List archived\nnode {skill}\u002Fscripts\u002Finbox.js list archived\n\n# Mark one read\nnode {skill}\u002Fscripts\u002Finbox.js read \u003Cid>\n\n# Mark all read\nnode {skill}\u002Fscripts\u002Finbox.js read-all\n\n# Archive one\nnode {skill}\u002Fscripts\u002Finbox.js archive \u003Cid>\n\n# Archive all read\nnode {skill}\u002Fscripts\u002Finbox.js archive-read\n\n# Render for chat (auto-detects channel via OPENCLAW_CHANNEL)\nnode {skill}\u002Fscripts\u002Finbox.js render [unread|all|archived]\n\n# Render as HTML (force)\nnode {skill}\u002Fscripts\u002Finbox.js render --html\n\n# Render as markdown (force)\nnode {skill}\u002Fscripts\u002Finbox.js render --md\n\n# Render as plain text (force)\nnode {skill}\u002Fscripts\u002Finbox.js render --text\n```\n\n## Presenting the Inbox\n\nWhen the operator asks to see their inbox (or says \"inbox\", \"messages\", \"check inbox\"), run:\n\n```bash\nnode {skill}\u002Fscripts\u002Finbox.js render [unread|all|archived] [--html|--md|--text]\n```\n\nChoose format based on channel:\n- **Telegram, webchat** → `--html`\n- **Discord, Slack** → `--md`\n- **SMS, plain** → `--text`\n\nSend the output as your reply. Do not add commentary unless they ask.\n\n## Heartbeat Integration\n\nDuring heartbeats, check for unread urgent\u002Fimportant items:\n\n```bash\nnode {skill}\u002Fscripts\u002Finbox.js list unread --json\n```\n\nIf urgent items exist, surface them proactively. Otherwise stay quiet.\n\n## Storage\n\nMessages stored in `{workspace}\u002Finbox\u002Fmessages.json`. Single-writer (the agent), so no locking needed. Writes use atomic rename (write .tmp → rename) to prevent corruption.\n\nEnvironment variables:\n- `OPENCLAW_WORKSPACE` — base directory for inbox storage (defaults to `$HOME`)\n- `OPENCLAW_CHANNEL` — used by `render` auto-format detection (telegram\u002Fdiscord\u002Fslack\u002Fwebchat)\n","# Operator Inbox\n\nA \"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.\n\n## Setup\n\nOn first use, the inbox file is created automatically at `{workspace}\u002Finbox\u002Fmessages.json`.\n\nRequires: `node` (Node.js runtime).\n\n## When to Write to the Inbox\n\nWrite an inbox entry when something is **notable enough that your operator would want to know, but not urgent enough to interrupt them.**\n\n### Write when:\n- **Needs decision** — something only a human can resolve (payment, approval, policy)\n- **Abnormal** — errors, failures, unexpected patterns, security events\n- **Interesting** — notable engagement, media mentions, milestones, opportunities\n- **FYI** — context that might matter later but needs no action now\n\n### Do NOT write when:\n- Routine success (\"cron ran fine\", \"heartbeat OK\")\n- Something you already told them in chat\n- Trivial events with no lasting significance\n- Duplicate of something already in the inbox\n\n### Priority levels:\n- `urgent` — needs attention within hours (prefix title with `[URGENT]`)\n- `important` — should see today (prefix title with `[IMPORTANT]`)\n- `normal` — whenever they check (no prefix)\n\n### Writing good entries:\n- **Title:** Short, scannable. Include the WHO or WHAT. (\"@bigaccount (500K) mentioned us\", not \"Social media event\")\n- **Message:** 1-3 sentences. What happened, why it matters, what (if anything) needs doing. Include links\u002Fhandles when relevant.\n\n## CLI Usage\n\n```bash\n# Add entry\nnode {skill}\u002Fscripts\u002Finbox.js add \"Title\" \"Description of what happened\"\n\n# Add with priority\nnode {skill}\u002Fscripts\u002Finbox.js add \"[URGENT] Server disk 95%\" \"Only 2GB remaining on \u002Fdev\u002Fsda1\"\n\n# List unread\nnode {skill}\u002Fscripts\u002Finbox.js list\n\n# List all (including read)\nnode {skill}\u002Fscripts\u002Finbox.js list all\n\n# List archived\nnode {skill}\u002Fscripts\u002Finbox.js list archived\n\n# Mark one read\nnode {skill}\u002Fscripts\u002Finbox.js read \u003Cid>\n\n# Mark all read\nnode {skill}\u002Fscripts\u002Finbox.js read-all\n\n# Archive one\nnode {skill}\u002Fscripts\u002Finbox.js archive \u003Cid>\n\n# Archive all read\nnode {skill}\u002Fscripts\u002Finbox.js archive-read\n\n# Render for chat (auto-detects channel via OPENCLAW_CHANNEL)\nnode {skill}\u002Fscripts\u002Finbox.js render [unread|all|archived]\n\n# Render as HTML (force)\nnode {skill}\u002Fscripts\u002Finbox.js render --html\n\n# Render as markdown (force)\nnode {skill}\u002Fscripts\u002Finbox.js render --md\n\n# Render as plain text (force)\nnode {skill}\u002Fscripts\u002Finbox.js render --text\n```\n\n## Presenting the Inbox\n\nWhen the operator asks to see their inbox (or says \"inbox\", \"messages\", \"check inbox\"), run:\n\n```bash\nnode {skill}\u002Fscripts\u002Finbox.js render [unread|all|archived] [--html|--md|--text]\n```\n\nChoose format based on channel:\n- **Telegram, webchat** → `--html`\n- **Discord, Slack** → `--md`\n- **SMS, plain** → `--text`\n\nSend the output as your reply. Do not add commentary unless they ask.\n\n## Heartbeat Integration\n\nDuring heartbeats, check for unread urgent\u002Fimportant items:\n\n```bash\nnode {skill}\u002Fscripts\u002Finbox.js list unread --json\n```\n\nIf urgent items exist, surface them proactively. Otherwise stay quiet.\n\n## Storage\n\nMessages stored in `{workspace}\u002Finbox\u002Fmessages.json`. Single-writer (the agent), so no locking needed. Writes use atomic rename (write .tmp → rename) to prevent corruption.\n\nEnvironment variables:\n- `OPENCLAW_WORKSPACE` — base directory for inbox storage (defaults to `$HOME`)\n- `OPENCLAW_CHANNEL` — used by `render` auto-format detection (telegram\u002Fdiscord\u002Fslack\u002Fwebchat)\n",{"name":5,"metadata":24,"description":7},{"openclaw":25},{"requires":26},{"env":27,"bins":30},[28,29],"OPENCLAW_WORKSPACE","OPENCLAW_CHANNEL",[31],"node","main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fdvdegenz\u002Fsnail-mail",1,"https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills","https:\u002F\u002Fgithub.com\u002Fjavimosch","intrane.fr","Building robust, open-source infrastructure for the commons. AI-leveraged, self-hosted, built to last.","2026-06-07 03:34:58",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill snail-mail",{"tool":47,"command":48},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill snail-mail",{"tool":50,"command":51},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill snail-mail","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdvdegenz\u002Fsnail-mail\u002FSKILL.md",true,[],[56,64,71,78,85,92],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":63},"01M778GGXG2VQ0YF31W2MKGMQZ","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.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":63},"01M778G7BH8SBJ9FJ6C3G7CB1K","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 \u003Csubcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir\u002FUltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":63},"01M778FYCJQZWFKKX5FYMK3S47","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 \u003Csubcommand>). 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\u002FUltraHonk zero-knowledge proofs.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser-send\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":63},"01M778FQQNSEYA3HJKZBPQ4M9Z","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).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":63},"01M778FGVZX7QA2TF9BFMM37FY","moldium","Post and manage content on the Moldium blog platform. Triggered by \"post to Moldium\", \"write a blog post\", \"publish an article\", etc.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyom45\u002Fmoldium\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":63},"01M778F88D8PQ9MQ0KNW2TJ8ZH","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\u002Fcategory\u002Finterest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http:\u002F\u002Fweakaccept.top:8000\u002F.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[],[]]