agentleFS
Martin-HausleitnerMartin-Hausleitner/martins-awesome-skills/skills/telegram-channel-poster/SKILL.md

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.

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
  1. Distinctive:

    Use this skill for outbound Telegram channel publishing through the native Telegram Bot API.

    line 8
  2. Distinctive:

    Never write bot tokens, channel secrets, or invite links into the skill.

    line 13
  3. Very specific:

    Keep Beeper separate: telegram-chats is for reading chats.

    line 15
  4. Very specific:

    Run the helper with --dry-run and inspect the redacted payload.

    line 43
  5. Very specific:

    If the user wants an audit trail, enable TELEGRAM_NOTION_LOG=true and dry-run the Notion payload.

    line 45
  6. Very specific:

    Verify the Telegram API response has "ok": true.

    line 47

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 @channelusername or the Bot API channel id.
  • Keep Beeper separate: telegram-chats is 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 MarkdownV2

Required 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

  1. Confirm the user requested an external Telegram post.
  2. Draft the exact message locally.
  3. Run the helper with --dry-run and inspect the redacted payload.
  4. For first-time setup, ask the user for the BotFather token and channel id, then store them outside the skill.
  5. If the user wants an audit trail, enable TELEGRAM_NOTION_LOG=true and dry-run the Notion payload.
  6. Send with the helper only after the publish intent is explicit.
  7. Verify the Telegram API response has "ok": true; if not, report the API error without exposing the token.

References

Tests

python3 scripts/test_telegram_channel_post.py

Download now (ZIP)

Does 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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.