Tg Bot Binding
Wire a personal Telegram bot to Starchild so your agent can push and receive messages outside the IDE.
Overview
tg-bot-binding is an agent skill for the Build phase that connects a Telegram bot to Starchild through BotFather creation, dashboard token binding, and in-chat verification.
Install
npx skills add https://github.com/starchild-ai-agent/official-skills --skill tg-bot-bindingWhat is this skill?
- Step-by-step BotFather flow to obtain and safeguard the bot token
- Starchild dashboard token entry and ownership verification in Telegram
- Troubleshooting paths for pushes not arriving and username whitelist issues
- 3-step binding overview: create bot, add token, verify in Telegram
- Responds in the user's language per SKILL.md
- 3 main binding steps: create bot, add token, verify ownership
Adoption & trust: 953 installs on skills.sh; 13 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want Starchild to deliver agent replies on Telegram but do not know how to create the bot, bind the token, or fix silent push failures.
Who is it for?
Solo builders using Starchild who need Telegram as the primary notify-and-chat channel for their agent.
Skip if: Teams building a custom Telegram backend without Starchild, or setups that only need webhook code with no dashboard binding flow.
When should I use this skill?
Setting up Telegram delivery (e.g. add my TG bot, bot binding code, fix "telegram not pushing", whitelist a TG username).
What do I get? / Deliverables
You end with a verified Telegram bot linked to Starchild and a clear checklist to resolve binding and whitelist issues.
- Bound Telegram bot connected to Starchild
- Verified ownership in Telegram
- Troubleshooting notes for push and whitelist issues
Recommended Skills
Journey fit
Binding a delivery channel is part of standing up agent infrastructure before you ship conversational workflows to users. Telegram bot tokens, BotFather setup, and Starchild dashboard verification are agent-tooling integration work, not generic backend CRUD.
How it compares
Use this procedural binding guide instead of guessing Starchild dashboard fields from generic Telegram Bot API tutorials.
Common Questions / FAQ
Who is tg-bot-binding for?
Starchild users and indie builders who want their AI agent reachable in Telegram via an official bot they control.
When should I use tg-bot-binding?
During Build when enabling agent-tooling integrations—e.g. first-time Telegram delivery, re-binding after token rotation, or debugging when Telegram stops pushing.
Is tg-bot-binding safe to install?
Treat bot tokens as secrets; review the Security Audits panel on this Prism page before installing and never paste tokens into public repos.
SKILL.md
READMESKILL.md - Tg Bot Binding
# Telegram Bot Binding Guide When the user asks about Telegram Bot binding, setup, connection, verification, or any related topic, provide them with the following guide. **Always respond in the user's language.** ## Overview Starchild allows you to connect your own Telegram Bot so you can interact with your AI agent directly in Telegram. The binding process involves 3 main steps: 1. Create a Bot on Telegram 2. Add the Bot Token in Starchild Dashboard 3. Verify ownership in Telegram --- ## Step-by-Step Binding Process ### Step 1: Create a Telegram Bot via BotFather 1. Open Telegram and search for **@BotFather** (the official Telegram bot for creating bots). 2. Send `/newbot` to BotFather. 3. Follow the prompts: - Enter a **display name** for your bot (e.g., "My Starchild Agent"). - Enter a **username** for your bot (must end in `bot`, e.g., `my_starchild_bot`). 4. BotFather will reply with your **Bot Token** — a string like `123456789:ABCdefGHIjklMNOpqrsTUVwxyz`. **Copy this token and keep it safe.** Do not share it publicly. ### Step 2: Add the Bot Token in Starchild Dashboard 1. Go to the **Starchild Dashboard** (web interface). 2. Click your **avatar** at the **bottom-left corner** of the page. 3. In the **Account Management** popup, find the **Telegram Bot** section. 4. Paste your **Bot Token** and submit. 5. The system will: - Verify the token with Telegram's API (calling `getMe`). - Generate a **6-digit verification code** (valid for 5 minutes). - Set the bot status to **"pending"**. 5. You will see the verification code displayed on the dashboard. **Copy this code.** ### Step 3: Verify Bot Ownership in Telegram You have two ways to verify: #### Option A: Deep Link (Recommended) Click the verification link provided on the dashboard. It will open your bot in Telegram and automatically submit the verification code. The link format is: ``` https://t.me/<your_bot_username>?start=verify_<CODE> ``` #### Option B: Manual Verification 1. Open your bot in Telegram (search for `@<your_bot_username>`). 2. Send `/start` — the bot will prompt you to enter the verification code. 3. Type the **6-digit code** and send it. ### Step 4: Done! Once verified, the bot status changes to **"active"** briefly, then automatically transitions to **"running"** — meaning your bot is live and ready. You can start chatting with your AI agent through Telegram. Send `/start` to see the welcome message and available commands. --- ## Bot Status Reference | Status | Meaning | |--------|---------| | `pending` | Bot token added, awaiting ownership verification | | `active` | Ownership verified, transitioning to running | | `running` | Bot is live and ready to use | | `deleted` | Bot has been removed by the user | --- ## Troubleshooting ### "Verification code expired" The verification code is valid for **5 minutes**. If it expires: - Go back to the Dashboard and click **"Refresh Code"** to generate a new one. - Then verify again in Telegram with the new code. ### "Too many failed attempts" After **5 incorrect attempts**, the verification code is invalidated for security: - Go to the Dashboard, **delete the bot**, and **add it again** to get a fresh code. ### "Bot token is already registered by another user" Each Bot Token can only be bound to one Starchild account. If you see this error: - Make sure you're using a **new, unused bot token**. - If you previously used this token, the old binding may still exist. Create a new bot via @BotFather. ### "You already have an active bot" Each account can only have **one active bo