Wechat Binding
- 2k installs
- 18 repo stars
- Updated July 27, 2026
- starchild-ai-agent/official-skills
wechat-binding is an agent skill for WeChat QR binding, connect, reconnect, and status checks enabling send_to_wechat delivery.
About
The wechat-binding skill documents WeChat account binding so agents can push messages via send_to_wechat after QR scan pairing. Typical flow is qrcode generation, user scan, qrcode_status poll after user confirms, then connect with bot_token on first bind or reconnect after dropped sessions. Actions table covers status, qrcode, qrcode_status, connect, disconnect, and reconnect with required parameters. Channel-aware QR display routes web inline file_path, Telegram send_to_telegram photo, or instruct web app when user is on WeChat. Critical rules forbid auto-polling qrcode_status before user says scanned, forbid reusing old qrcode ids, never paste bot_token in chat, and confirm before destructive disconnect. connect is first-time binding while reconnect restores prior sessions after ilink expiry. References messaging-channels.md for post-bind sending and analogous tg-bot-binding skill. Use when setting up or repairing WeChat delivery, scan QR, or diagnosing missing WeChat push.
- Flow: qrcode, user scan confirm, qrcode_status, connect or reconnect.
- Actions: status, qrcode, qrcode_status, connect, disconnect, reconnect.
- Channel-aware QR display for web, Telegram, or WeChat contexts.
- Never auto-poll qrcode_status or expose bot_token in chat.
- connect vs reconnect based on status and prior binding history.
Wechat Binding by the numbers
- 2,009 all-time installs (skills.sh)
- +60 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #185 of 2,742 Automation & Workflows skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
wechat-binding capabilities & compatibility
- Capabilities
- qr generate and status polling workflow · connect versus reconnect decision logic · channel aware qr display routing · credential hygiene for bot_token · destructive disconnect confirmation
- Use cases
- orchestration · email · planning
What wechat-binding says it does
WeChat binding: QR scan, bind, unbind, reconnect, status check.
npx skills add https://github.com/starchild-ai-agent/official-skills --skill wechat-bindingAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2k |
|---|---|
| repo stars | ★ 18 |
| Security audit | 2 / 3 scanners passed |
| Last updated | July 27, 2026 |
| Repository | starchild-ai-agent/official-skills ↗ |
How do I bind WeChat for agent message push with QR scan and connect workflow?
Connect, reconnect, and disconnect WeChat delivery via QR scan, qrcode_status polling, and connect or reconnect actions for send_to_wechat messaging.
Who is it for?
Developers setting up agent WeChat message delivery and repairing dropped WeChat connections.
Skip if: Skip when WeChat push is not needed or another messaging channel is already bound.
When should I use this skill?
Use when setting up WeChat delivery, scan QR, why isn't WeChat pushing, or disconnect WeChat.
What you get
WeChat connected with bot_token passed to connect or reconnect and push-ready send_to_wechat.
- Bound WeChat connection
- Status verification steps
By the numbers
- Skill version 1.0.1 from starchild-ai-agent/official-skills
Files
📱 WeChat Binding
Connect / reconnect / disconnect the user's WeChat account so the agent can push messages via send_to_wechat.
The wechat tool stays built-in. This SKILL.md is the reference doc.
See also
config/context/references/messaging-channels.md— how to actually send messages once boundskills/tg-bot-binding/SKILL.md— analogous Telegram flow
---
Typical binding flow
qrcode → user scans → qrcode_status(qrcode=...) → connect(bot_token=...)1. Generate QR: wechat(action="qrcode") — saves an image to workspace, returns qrcode (id) + file_path. 2. Show the QR to the user. On web channel: include the file_path so the frontend renders the image. On TG/WeChat channel: send the image via send_to_telegram with the file_path. 3. Wait for the user to scan + confirm in WeChat. Don't auto-poll — let them say "scanned" / "done" first. 4. Poll for completion: wechat(action="qrcode_status", qrcode=<id from step 1>). Returns bot_token once scan + confirm completes. 5. Connect: wechat(action="connect", bot_token=<from step 4>). Optional: ilink_bot_id, ilink_user_id if the user has multiple WeChat accounts. 6. Confirm to user: "WeChat connected. You can now push messages with send_to_wechat."
---
Actions
| action | required | purpose |
|---|---|---|
status | — | Current WeChat connection state. Use before reconnect, to verify binding. |
qrcode | — | Generate QR code image (saved to workspace). Returns qrcode id + file_path. |
qrcode_status | qrcode | Poll whether user has scanned + confirmed. Returns bot_token on success. |
connect | bot_token | Complete a NEW WeChat connection (after first-ever QR scan). Optional: ilink_bot_id, ilink_user_id. |
disconnect | — | Terminate current WeChat session (unlink). |
reconnect | bot_token | Re-establish a previously-bound WeChat (token from a fresh QR scan). |
---
connect vs. reconnect
- `connect` — first-time binding. The user has NEVER bound this WeChat before.
- `reconnect` — the user was previously connected, the connection dropped (e.g. ilink session expired), and they just scanned a fresh QR.
When in doubt, call status first:
connected: false+ no prior history →connectconnected: false+ prior history exists →reconnect
---
Channel-aware QR display
| User channel | How to show the QR |
|---|---|
| Web | Include file_path in your reply — frontend renders it inline |
| Telegram | send_to_telegram(file_path=<qr_path>, message_type="photo") |
| (You can't — they're trying to bind WeChat in the first place. Tell them to open the web app.) |
---
Critical rules
- Don't auto-poll
qrcode_statusafterqrcode. Wait for user confirmation that they scanned + confirmed in WeChat. Auto-polling spams the upstream API. - Each `qrcode` call generates a fresh image. Don't re-use an old
qrcodeid with a new image — the upstream session is tied to the id. - Never paste `bot_token` in chat. It's a credential. Once you have it from
qrcode_status, immediately pass it toconnect/reconnectand don't echo it back to the user. - `disconnect` is destructive — confirm with the user before calling it.
Related skills
Agent BrowserGive their coding agent reliable, high-fidelity control over any website or Electron desktop app.577k39.1k
Lark ApprovalLet their AI coding agent create, read, update, and approve items in Lark (Feishu) approval workflows without leaving the coding environment.471kLark EventHandle Feishu/Lark bot events, webhooks, and subscription callbacks in agent-driven backend code.471kLark Workflow Meeting SummaryAutomatically generate structured meeting summaries and action items from Lark/Feishu calls without manual note-taking.470kLark Workflow Standup ReportAutomatically generate and post daily standup reports in Lark/Feishu from their workflow and activity data.470kLark Vc AgentGive their coding agent the ability to read, create, and update documents, tasks, and wiki pages inside Feishu (Lark).415kHow it compares
Use wechat-binding for Starchild WeChat QR flows rather than tg-bot-binding when the delivery channel must be WeChat.
FAQ
Who is wechat-binding for?
Developers and software engineers setting up agent WeChat message delivery and repairing dropped WeChat connections.
When should I use wechat-binding?
When setting up WeChat delivery, scan QR, why isn't WeChat pushing, or disconnect WeChat.
Is wechat-binding safe to install?
Review the Security Audits panel on this page before installing in production.