Notify Wecom Skill for Claude
>- 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.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/daymade/claude-code-skills --skill notify-wecomThe instruction itself
8 sections, as written by the author/notify-wecom
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.
Other skills for the same job
different authors, same section of the catalogue
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Replace with description of the skill and when Claude should use it.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Use when executing implementation plans with independent tasks in the current session
How to use it
Take daymade/notify-wecom from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.