wecom-notify

backendxueheng-li

Send messages to WeCom (企业微信) via the WeCom API. Use when the user asks to "send wecom message", "notify via wecom", "发企业微信", "给我发企业微信消息", "wecom通知", "发文件到企业微信", "发图片到企业微信", or when a task completes and the user wants notification on WeCom.

Install

npx skills add https://github.com/xueheng-li/openclaw-wechat --skill wecom-notify

SKILL.md

---name: wecom-notifydescription: Send messages to WeCom (企业微信) via the WeCom API. Use when the user asks to "send wecom message", "notify via wecom", "发企业微信", "给我发企业微信消息", "wecom通知", "发文件到企业微信", "发图片到企业微信", or when a task completes and the user wants notification on WeCom.---

WeCom Notify

Send text, image, or file messages to WeCom (企业微信) using scripts/send_wecom.py.

Usage

# Text message
python3 scripts/send_wecom.py "消息内容"
python3 scripts/send_wecom.py "消息内容" --to LiXueHeng

# Image message
python3 scripts/send_wecom.py --image /path/to/photo.png
python3 scripts/send_wecom.py --image /path/to/chart.jpg --to @all

# File message
python3 scripts/send_wecom.py --file /path/to/report.pdf
python3 scripts/send_wecom.py --file /path/to/data.xlsx --to LiXueHeng

Default recipient: LiXueHeng. Config is read from ~/.openclaw/openclaw.json (env.vars section).

Notes

Requires proxy (WECOM_PROXY in config) — API calls route through Guangzhou VPS tinyproxy at 10.147.17.105:8888 via ZeroTier
WeCom text messages have a 2048-byte limit (~680 Chinese characters). For longer messages, split into multiple sends
Image upload supports: jpg, png, gif (max 2MB for image type)
File upload supports: any format (max 20MB)
Uploaded media is temporary (3 days validity on WeCom servers)
The script uses only Python stdlib (urllib.request, json, mimetypes, uuid) — no pip dependencies

Related skills

entra-app-registrationmicrosoft606KGuides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.azure-messagingmicrosoft595KTroubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. WHEN: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue, message lock lost, message lock expired, lock renewal, lock renewal batch, send timeout, receiver disconnected, SDK troubleshooting, azure messaging SDK, event hub consumer, servic entra-agent-idmicrosoft328KProvision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmi_path, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmi_path token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app regist supabasesupabase298KUse when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, declarative schemas, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector); deb