notify-wecom
Send a single one-off message to a WeCom (Enterprise WeChat) group bot. Use this skill whenever the user says "/notify-wecom", "send a quick WeCom message", "企微通知一下", "临时发一条企业微信", or any one-shot notification that does not need a reusable template or setup workflow. The message is sent immediately; no confirmation prompt is shown unless the message is empty or the webhook is not configured.
pinned to #029876dupdated last month
Ask your AI client: “install skills/notify-wecom”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/notify-wecommetahub onboarded this repo on the author's behalf.
If you own github.com/daymade/claude-code-skills on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
1,331
Last commit
last month
Latest release
published
About this skill
Pulled from SKILL.md at publish time.
Send a single message to a WeCom group bot.
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.029876d· last month
Documentation
7 passed2 warningsTags / topics declaredwarn
No manifest tags and no GitHub repo topics
Add tags to the manifest (or GitHub topics on the repo) so the registry's search and category filters surface this artifact.
Homepage or repository declaredwarn
No homepage or repository declared.
Add a "homepage" or "repository" field to SKILL.md.
Description quality
77 words · 393 chars — "Send a single one-off message to a WeCom (Enterprise WeChat) group bot. Use this…"
README is present and substantial
182,381 chars · 15 sections · 88 code blocks
README has usage / example sections
found: Example
Homepage / docs URL declared
no homepage declared (registry will use the repo URL) — info-only, not blocking
Description is substantive
Description is 79 words.
Documentation present and substantive
Documentation present (SKILL.md, 363 words).
Documentation shows usage
Documentation includes 4 code examples.
Release history
1- releasecurrent029876dwarnlast month
Contents
Send a single message to a WeCom group bot.
Usage
/notify-wecom Claude Code 备份完成 ✅
The skill reads the webhook URL from the shared config file:
~/.config/setup-notifications-via-wecom/config.json
If the config is missing, it prints the one-line setup command and stops.
Prerequisite
This skill is a lightweight companion to setup-notifications-via-wecom. Either:
- Install
setup-notifications-via-wecomfirst (recommended — it provides the webhook setup steps and its bundled sender), or - Create the config file manually as shown below.
What It Does
- Reads
~/.config/setup-notifications-via-wecom/config.jsonforwebhook_url. - Unsets all local proxy env vars (Tencent endpoints must be reached directly).
- Sends the message via the WeCom webhook using the sender from
setup-notifications-via-wecom(or an equivalent inline curl call). - Reports success or the exact WeCom error.
Examples
/notify-wecom 服务上线成功 🚀
/notify-wecom 告警:build 失败,请检查
/notify-wecom 今日同步完成,0 缺失 0 滞后
Multi-line Messages
For multi-line messages, wrap in triple quotes or use a file:
/notify-wecom "第一行
第二行
第三行"
Failure Modes
- Config missing: Run the setup step from
setup-notifications-via-wecom, or create the config file manually. - Webhook key invalid: WeCom returns an
errcode; the skill prints it. - Proxy still interfering: If you have proxy vars set outside the standard names, unset them first.
Limitations
- Plain text only. No markdown cards, images, or @mentions.
- Message length limit is 4096 bytes (UTF-8).
- No templating — use
setup-notifications-via-wecomfor structured backup/alert/status messages.
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/notify-wecom