telegram-channel-poster
Skill3 starsChanged 6 months agoMITView on GitHub
Use when the user asks to publish, post, announce, syndicate, or automatically send content to a Telegram channel using a native Telegram bot rather than Beeper chat lookup.
In this repository34 other files it gives its agents.
- tool-comparison-heatmapSkill
- ascii-artSkill
- excalidrawSkill
- p5jsSkill
- songwriting-and-ai-musicSkill
- webhook-subscriptionsSkill
- himalayaSkill
- github-authSkill
- github-code-reviewSkill
- github-issuesSkill
- github-pr-workflowSkill
- find-nearbySkill
- native-mcpSkill
- songseeSkill
- youtube-contentSkill
- ai-research-output-publisherSkill
- notionSkill
- ocr-and-documentsSkill
- arxivSkill
- blogwatcherSkill
- comparison-deep-researchSkill
- polymarketSkill
- multi-search-engineSkill
- ai-research-browser-cliSkill
- ai-research-browserSkill
- cross-agent-skill-syncSkill
- oracle-ai-research-e2eSkill
- planSkill
- requesting-code-reviewSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- writing-plansSkill
- telegram-approval-gateSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill for outbound Telegram channel publishing through the native Telegram Bot API.
- Distinctive: line 13
Never write bot tokens, channel secrets, or invite links into the skill.
- Very specific: line 15
Keep Beeper separate: telegram-chats is for reading chats.
- Very specific: line 43
Run the helper with --dry-run and inspect the redacted payload.
- Very specific: line 45
If the user wants an audit trail, enable TELEGRAM_NOTION_LOG=true and dry-run the Notion payload.
- Very specific: line 47
Verify the Telegram API response has "ok": true.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Telegram Channel Poster
Use this skill for outbound Telegram channel publishing through the native Telegram Bot API.
Safety
- Posting is external communication. If the user did not explicitly ask to publish in this turn, prepare a dry run and ask before sending.
- Never write bot tokens, channel secrets, or invite links into the skill. Load them from a private env file, Keychain, or OpenClaw secrets.
- The bot must be an administrator in the target channel. Use
@channelusernameor the Bot API channel id. - Keep Beeper separate:
telegram-chatsis for reading chats; this skill is for native bot/channel publishing.
Helper
./scripts/telegram_channel_post.sh --dry-run --text "Hello"
./scripts/telegram_channel_post.sh --text "Hello"
./scripts/telegram_channel_post.sh --file /path/to/message.md --parse-mode MarkdownV2Required env file shape:
TELEGRAM_BOT_TOKEN="123456:token-from-botfather"
TELEGRAM_CHANNEL_ID="@channelusername"Optional Notion logging uses the notion-openclaw-log skill:
TELEGRAM_NOTION_LOG="true"
NOTION_PARENT_PAGE_ID="page-id-shared-with-integration"Workflow
- Confirm the user requested an external Telegram post.
- Draft the exact message locally.
- Run the helper with
--dry-runand inspect the redacted payload. - For first-time setup, ask the user for the BotFather token and channel id, then store them outside the skill.
- If the user wants an audit trail, enable
TELEGRAM_NOTION_LOG=trueand dry-run the Notion payload. - Send with the helper only after the publish intent is explicit.
- Verify the Telegram API response has
"ok": true; if not, report the API error without exposing the token.
References
- Telegram Bot API
sendMessage: https://core.telegram.org/bots/api#sendmessage - Telegram Bot API dialog ids: https://core.telegram.org/api/bots/ids
- Optional local Notion log skill, configured via
NOTION_HELPER.
Tests
python3 scripts/test_telegram_channel_post.pyDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

