telegram-bot-maker
Build and operate Telegram bots with BotFather, HTTPS webhooks, n8n workflows, and SCBE connector automation. Use when users ask to create, wire, debug, or harden Telegram bot pipelines.
Best use case
telegram-bot-maker is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Build and operate Telegram bots with BotFather, HTTPS webhooks, n8n workflows, and SCBE connector automation. Use when users ask to create, wire, debug, or harden Telegram bot pipelines.
Teams using telegram-bot-maker should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/telegram-bot-maker/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How telegram-bot-maker Compares
| Feature / Agent | telegram-bot-maker | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Build and operate Telegram bots with BotFather, HTTPS webhooks, n8n workflows, and SCBE connector automation. Use when users ask to create, wire, debug, or harden Telegram bot pipelines.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Telegram Bot Maker ## Overview Use this skill to move from bot token to working Telegram automation quickly: - BotFather token + webhook configuration. - n8n workflow setup for inbound/outbound bot behavior. - SCBE connector registration and health checks. - Basic hardening and troubleshooting. ## Trigger Conditions Use this skill when users ask to: - Create a Telegram bot. - Set or fix Telegram webhook URLs. - Connect Telegram to n8n workflows. - Add Telegram into SCBE connector matrix, watchdog, or fleet bootstrap. - Troubleshoot errors like `https is required`, `404`, `chat not found`, `unauthorized`. ## Required Inputs - `TELEGRAM_BOT_TOKEN` (or `SCBE_TELEGRAM_BOT_TOKEN`) - Public HTTPS webhook URL - Optional `TELEGRAM_CHAT_ID` (numeric) for send tests - n8n endpoint details when routing to n8n - SCBE base URLs for connector registration (`/mobile/connectors`) ## Workflow ### 1) Validate public endpoint first Run URL checks before setting webhook: ```powershell curl.exe -I https://<your-host>/<webhook-path> ``` If endpoint is not reachable, do not proceed with BotFather webhook setup. ### 2) Set/get/delete webhook using bundled script Use: - `scripts/telegram_webhook_ops.ps1` Examples: ```powershell powershell -ExecutionPolicy Bypass -File scripts/telegram_webhook_ops.ps1 -Action set -WebhookUrl "https://<your-host>/webhook/<path>" powershell -ExecutionPolicy Bypass -File scripts/telegram_webhook_ops.ps1 -Action get powershell -ExecutionPolicy Bypass -File scripts/telegram_webhook_ops.ps1 -Action test -ChatId "<numeric_chat_id>" -Message "SCBE test ping" ``` ### 3) Build n8n Telegram workflow Start from `references/n8n_telegram_rag_blueprint.md`: - Convert generic triggers to Telegram Trigger + Telegram send nodes. - Keep embeddings/vector operations aligned between insert/retrieve. - Replace in-memory vector store with persistent storage for production. ### 4) Wire Telegram into SCBE In `SCBE-AETHERMOORE`: ```powershell python scripts/connector_health_check.py --checks telegram --telegram-chat-id $env:TELEGRAM_CHAT_ID --output artifacts/connector_health/telegram_health.json powershell -ExecutionPolicy Bypass -File scripts/system/register_connector_profiles.ps1 -Profile free -BaseUrl http://127.0.0.1:8000 -N8nBaseUrl http://127.0.0.1:5680 -ReplaceExisting ``` ### 5) Hardening defaults - Use numeric Telegram user/chat IDs for allowlists and tests. - Keep bot token in environment or CI secret store only. - Require HTTPS endpoints only. - Prefer group mention gating when deploying to group chats. ## References - `references/n8n_telegram_rag_blueprint.md` ## Scripts - `scripts/telegram_webhook_ops.ps1` ## Output Contract When completing a bot setup, return: - `webhook_url` - `webhook_state` (`set`/`missing`/`error`) - `n8n_workflow_status` - `scbe_connector_status` - `next_command`
Related Skills
scbe-doc-maker
Build local-first fiction and non-fiction documents from SCBE sources with verifiable citations, structured outlines, and export-ready artifacts. Use when asked to draft, revise, synthesize, or package books, reports, specs, or training corpora from repo/wiki/notes.
scbe-training-pair-authoring
Create prompt and response and metadata training pairs from SCBE documents, repair traces, terminal sessions, and operational workflows using the repository's canonical dataset contract and provenance rules.
scbe-spin-conversation-engine
Generate SFT training data via radial matrix conversation pivots with D&D-style combat research mode. Produces diverse, cost-effective training pairs with Sacred Tongue encoding, golden spiral problem distribution, and harmonic re-attunement.
scbe-research-training-bridge
Stage arXiv evidence and Obsidian markdown into source-grounded Hugging Face training bundles for research, review, and later SFT runs.
scbe-document-management
Consolidate overlapping docs, classify files by authority, and keep SCBE repo documents aligned with runtime truth. Use when the repo has drift between canonical docs, public docs, proposal notes, research branches, and generated evidence.
scbe-colab-bridge
Control Google Colab notebooks from Claude Code via Chrome extension. Execute cells, run terminal commands, read outputs, and manage GPU compute remotely.
scbe-claim-to-code-evidence
Map SCBE Notion technical claims, proof pages, and patent-facing architecture notes to concrete repository evidence such as code paths, tests, demos, and docs. Use when Codex needs to build a due-diligence packet, claim-to-code audit, implementation crosswalk, patent support note, or proof summary from local Notion exports and repo artifacts.
scbe-autonomous-worker-productizer
Turn SCBE automation, autonomous worker, and revenue-system notes into concrete offers, workflow packs, pilot plans, or SaaS-facing product packets. Use when Codex needs to package Notion automation pages into buyer-ready offerings, n8n/Zapier workflow designs, flock-backed worker systems, or implementation roadmaps tied to existing SCBE repo surfaces.
multi-agent-cloud-offload
Deterministically sort, bundle, verify, and offshore local files through multiple AI/model lanes while capturing training rows and method evidence. Use when Codex needs to inventory folders, batch-process files, upload them to cloud targets such as rclone-backed Google Drive, Hugging Face, or GitHub, and only delete sources after the configured number of verified targets succeed.
long-form-work-orchestrator
Run long-form engineering work in checkpointed phases with deterministic artifacts, resilience handling, and end-of-run reliability reporting.
scbe-code-scanning-ops
Operate GitHub code scanning and CodeQL remediation for SCBE repositories. Use when triaging code-scanning alerts, mapping alert classes to fix patterns, validating targeted regressions, or wiring dedicated CodeQL workflows and runbooks into the repo.
cloud-storage-local-storage-management
Audit, sort, route, and back up large Windows workspaces across local disks and cloud-sync folders without recursive mirror failures. Use when the user wants the filesystem cleaned up, cloud storage organized, backup targets chosen by free space and route quality, or hardware/storage bottlenecks identified before moving data.