skill-publish-notify · Publish Notifications
After content publishes (or fails), push the result to Feishu, DingTalk, WeCom group bots, Telegram, Slack, or any webhook.
Six channels (feishu / dingtalk / wecom / telegram / slack / generic), pure standard-library script, zero third-party dependencies. Typically chained with publishing skills: success pushes "published + link", failure pushes the error. Dry-run previews the payload before sending.
Example invocation: "Push the result to our Feishu group after publishing."
Full brief
Positioning
skill-publish-notify is the notification step of the publish flow: after the publish action completes, it pushes the result to the team's IM. It only sends notifications — not the publishing itself.
Core capabilities
- Six channels: Feishu/Lark (rich-text titles), DingTalk (optional signature secret), WeCom, Telegram (bot token + chat_id), Slack (Incoming Webhook), generic (any webhook receiving
{"text": ...}). - Pure standard library: no third-party dependencies; every channel follows the standard POST-JSON-to-webhook protocol.
- Dry-run preview: inspect the payload before sending; user confirms content and target group.
- Success criteria: HTTP 200 plus each provider's success code, otherwise prompts to check the webhook.
Workflow
- Pick the channel and webhook / token (from user config or .env — never hardcoded)
- Compose the notice: status + title + platform + link
--dry-runpreview; user confirms- Send; judge by each provider's success code
Inputs & outputs
| Input | Required | Notes |
|---|---|---|
| Channel | Yes | feishu / dingtalk / wecom / telegram / slack / generic |
| webhook / token | Yes | Group-bot URL (Telegram: token + chat_id) |
| Notice content | Yes | Body, optional title |
Output: push result (success / failure).
Boundaries with adjacent skills
- This skill is post-publish notification; publishing itself lives in per-platform publish skills (e.g. skill-douyin-upload, skill-xhs-publisher); publish records live in skill-publish-log.
Fit
- Auto-notifying the ops group after content publishes
- Alerting the on-duty group on publish failures
- Unified result summaries after multi-platform distribution
Before you start
- No API key; needs each channel's group-bot webhook / token (sensitive — read from .env, never leaked).
- Rules:
--dry-runfirst so the user confirms content and target group; DingTalk groups with signature security must pass--secret; keep notices tight: status + title + platform + link.
skill-publish-notify is part of the Aiglade Skill library. Invoke it from the Aiglade chat box in plain language.