syndicate-notify
GitHub将运行摘要发送至 Telegram。使用前需验证环境变量，通过 stdin 传入 OrchestratorResult JSON 执行发送，成功返回确认信息，失败则报错。
Trigger Scenarios
Install
npx skills add NeverSight/learn-skills.dev --skill syndicate-notify -g -y
SKILL.md
Frontmatter
{
"name": "syndicate-notify",
"context": "inline",
"description": "Post a run summary to Telegram. External side-effect (sends a message to the configured chat).",
"when_to_use": "When the user explicitly asks to \"send the run summary to Telegram\",\n\"notify Telegram\", or \"post the digest stats\". Usually invoked manually\nto re-send a missed summary; the orchestrator run already auto-notifies.\n",
"allowed-tools": [
"Bash(uv run python -m pipeline.cli notify*)",
"Bash(uv run python -m pipeline.cli status*)",
"Bash(cd:*)",
"Read"
],
"disable-model-invocation": true
}
/syndicate-notify
You are sending a Telegram message. External side-effect — only run when the user explicitly asked.
Step 1 — preflight
Run status and confirm env_present.TELEGRAM_BOT_TOKEN and
env_present.TELEGRAM_CHAT_ID are both true. If not, point the user at
the bot setup docs
and stop.
Step 2 — send
The notify subcommand reads an OrchestratorResult JSON from stdin. If the
user has a recent cli run output handy (e.g. from a prior session log
or a file they pass), pipe it in:
cd "${SYNDICATE_REPO:-$(pwd)}" && cat path/to/run-result.json | uv run python -m pipeline.cli notify
If the user just wants to re-send the LAST run summary without a stored
JSON, ask them to run /syndicate-run instead — that path notifies
automatically and is the canonical way to refresh the Telegram feed.
Output envelope:
{"ok": true, "result": {"ok": true}, "log_path": null}
Step 3 — report
One line: ✓ telegram notified on success, otherwise show the error.
Version History
- e0220ca Current 2026-07-05 22:03
