notify wecom

Other Community

Skill notes

Usage

The skill reads the webhook URL from the shared config file: 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

Reads ~/.config/setup-notifications-via-wecom/config.json for webhook_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.

Multi-line Messages

For multi-line messages, wrap in triple quotes or use a file:

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.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@daymade · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Env read
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# /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.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.