wechat-binding
WeChat binding: QR scan, bind, unbind, reconnect, status check. Use when setting up or repairing WeChat delivery (e.g. connect WeChat, scan QR, why isn't WeChat pushing, disconnect WeChat).
What this skill does
# ๐ฑ 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 bound - `skills/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 โ `connect` - `connected: 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")` | | **WeChat** | (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_status` after `qrcode`. 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 `qrcode` id 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 to `connect` / `reconnect` and don't echo it back to the user. - **`disconnect` is destructive** โ confirm with the user before calling it.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.