You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: scenarios as agent prompts, not CLI commands
The user talks to their agent in natural language. The agent uses the
skill internally. Scenarios should show what you SAY to your agent,
not what wxclawbot commands to run. The CLI reference section is for
the agent and scripts, not for humans.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Let your OpenClaw AI agent proactively send WeChat messages. Text, images, video, files -- whatever you need.
5
+
Let your OpenClaw AI agent proactively send WeChat messages. Text, images, video, files.
6
6
7
7
## Why This Exists
8
8
9
-
WeChat's official bot API has one glaring limitation: bots can only *reply*. They can't initiate conversations. It's like hiring an assistant who only speaks when spoken to. Completely useless for reminders, alerts, or anything proactive.
9
+
WeChat's bot API only supports replies -- bots can't initiate. This skill fixes that. Your agent can now send messages on its own schedule.
10
10
11
11
> "Currently doesn't support proactively sending you messages on a schedule"
**This CLI fixes that.** Your OpenClaw agent can now send messages on its own schedule -- timed reminders, monitoring alerts, automated reports. Reuses [openclaw-weixin](https://www.npmjs.com/package/@tencent-weixin/openclaw-weixin) credentials, no extra auth dance.
15
+
## How It Works
16
16
17
-
## What Can It Actually Do?
18
-
19
-
### Life Reminders (Before Your Body Reminds You the Hard Way)
17
+
### 1. Install the skill
20
18
21
19
```bash
22
-
# Every 45 minutes
23
-
wxclawbot send --text "Drink water. Don't wait for kidney stones to remind you." --json
24
-
25
-
# Every hour of sitting
26
-
wxclawbot send --text "Your ass has been welded to that chair for 60 minutes. Stand up." --json
27
-
28
-
# 1 AM and still coding
29
-
wxclawbot send --text "Your code quality is receding faster than your hairline. Go to sleep." --json
30
-
31
-
# Friday 5:55 PM
32
-
wxclawbot send --text "5 minutes to freedom. Don't accept new tasks. Don't reply to messages. Prepare to run." --json
33
-
34
-
# Weekdays 11:15 AM
35
-
wxclawbot send --text "Order lunch now or delivery gets backed up until 2 PM. Enjoy hunger-driven development." --json
20
+
clawhub install wxclawbot-send
36
21
```
37
22
38
-
### DevOps (Know When Production Is on Fire)
39
-
40
-
```bash
41
-
# CI/CD broke
42
-
wxclawbot send --text "CI is down. It was @zhangsan's commit abc1234. Please clean up your mess." --json
43
-
44
-
# PR sitting unreviewed for 24h
45
-
wxclawbot send --text "PR #42 has been sitting there for 24 hours. Review it. Code doesn't merge itself." --json
23
+
### 2. Just talk to your agent
46
24
47
-
# Deploy succeeded
48
-
wxclawbot send --text "v2.3.1 is live. Nothing has exploded yet." --json
25
+
No code, no cron config, no CLI. The agent handles scheduling and invocation internally.
{"ok":false,"error":"ret=-2 (rate limited, try again later)"}
122
94
```
123
95
124
-
**Exit code 0 means the CLI ran successfully. It does NOT mean the message was delivered.** Always check the `ok` field. Yes, this violates the spirit of Unix exit codes. Reality doesn't care about your principles -- network calls and local execution are different things.
125
-
126
-
## Errors
96
+
| ret | meaning | action |
97
+
|-----|---------|--------|
98
+
| -2 | rate limited | wait 5-10s, retry |
99
+
| -14 | session expired | re-login via openclaw |
127
100
128
-
| ret | meaning | what to do |
129
-
|-----|---------|------------|
130
-
| -2 | rate limited | Wait 5-10 seconds and retry. Do not `while true` loop this. That makes it worse. |
131
-
| -14 | session expired | Re-login via openclaw. Tokens don't last forever. |
132
-
133
-
Rate limit: **~7 messages / 5 minutes** per bot account, enforced server-side, shared across all clients. No, you can't bypass it with multiple processes. Don't try.
0 commit comments