# /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-wecom` first (recommended — it provides the webhook setup steps and its bundled sender), or
- Create the config file manually as shown below.

## What It Does

1. Reads `~/.config/setup-notifications-via-wecom/config.json` for `webhook_url`.
2. Unsets all local proxy env vars (Tencent endpoints must be reached directly).
3. Sends the message via the WeCom webhook using the sender from `setup-notifications-via-wecom` (or an equivalent inline curl call).
4. 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-wecom` for structured backup/alert/status messages.