Name: active-telegram-message
Author: j4ch3n

Imported from j4ch3n/Battuta (bots/pm-bot/.pi/skills/active-telegram-message/SKILL.md). Install upstream with npx skills add j4ch3n/Battuta --skill active-telegram-message. Copyright stays with the author.

Active Telegram message

Use the existing @llblab/pi-telegram bridge for an intentional outbound update. This skill is for an explicit request to send a message, not for every internal agent-mail exchange.

If answering the human's active Telegram turn, write the response normally. The bridge delivers that reply; do not also call telegram_message for the same target.
When the request calls for a separate message from a local or autonomous Pi turn, use the bridge's telegram_message tool. Check that the bridge is connected and has a current authorized target; do not invent a chat ID or thread. Report delivery failure instead of claiming it was sent.
For a progress note, say what is being checked and why a response may take time. For a substantive result, briefly summarize the finding, any decision needed, and the next step. Do not forward raw agent mail or duplicate a message already projected by the bridge's connected companion delivery.

telegram_message is direct delivery; a final answer from an autonomous Pi turn may also be projected to the same Telegram target. Choose one route for each piece of content to avoid duplicates. Never start a second Telegram polling client.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

{ "ocm": "1", "id": "j4ch3n-battuta-active-telegram-message", "kind": "skill", "name": "active-telegram-message", "description": "Send an explicit, proactive Telegram message from the PM's connected Pi session when asked to notify the human outside the normal reply to a Telegram turn.", "publisher": "j4ch3n", "version": "1.0.0", "capabilities": { "domains": [ "customer_support" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Send an explicit, proactive Telegram message from the PM's connected Pi session when asked to notify the human outside the normal reply to a Telegram turn." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/j4ch3n/Battuta", "path": "bots/pm-bot/.pi/skills/active-telegram-message/SKILL.md", "ref": "ab3f7f407cee6493d583c89edc4838f54e58f8b1", "url": "https://github.com/j4ch3n/Battuta/blob/ab3f7f407cee6493d583c89edc4838f54e58f8b1/bots/pm-bot/.pi/skills/active-telegram-message/SKILL.md", "key": "j4ch3n/Battuta/bots/pm-bot/.pi/skills/active-telegram-message/SKILL.md" } }, "instructions": "# Active Telegram message\n\nUse the existing `@llblab/pi-telegram` bridge for an intentional outbound update. This skill is for an explicit request to send a message, not for every internal agent-mail exchange.\n\n1. If answering the human's active Telegram turn, write the response normally. The bridge delivers that reply; do not also call `telegram_message` for the same target.\n2. When the request calls for a separate message from a local or autonomous Pi turn, use the bridge's `telegram_message` tool. Check that the bridge is connected and has a current authorized target; do not invent a chat I", "cost": { "context_tokens": 302 } }

active-telegram-message

About

Active Telegram message

Use it

Manifest

Reviews