Menu
Check Telegram bot configuration and guide setup if anything is missing.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/oimiragieo/agent-studio --skill setup-telegramThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Agent frontmatter enhancements — disallowedTools, mcpServers scoping, fork_eligible field
Context management — pre-compact persistence, threshold alignment, microcompact/circuit breaker detection
Hook enhancements — updatedInput for bash safety prefixes, suppressOutput for verbose blocks, denial-based routing feedback
Showing SKILL.md
Based on SOC occupation classification
| name | setup-telegram |
| version | 1.3.0 |
| description | Check Telegram bot configuration and guide setup if anything is missing. |
| category | infrastructure |
| trigger | when user says /setup-telegram, "setup telegram", "configure telegram bot" |
| tools | ["Read"] |
| tags | ["telegram","setup","configuration"] |
| invoked_by | user |
| user_invocable | true |
| error_handling | graceful |
| verified | true |
| source | builtin |
| trust_score | 100 |
| provenance_sha | be8990003effcb06 |
Check if the Telegram bot is properly configured by reading config files. Do NOT use Bash — use the Read tool only.
Read each of these files and verify the required values:
Read .env in the project root. Check for:
TELEGRAM_BOT_TOKEN — must exist and be non-emptyTELEGRAM_OWNER_ID — must exist (numeric Telegram user ID)CHANNEL_AUTO_START — must be trueCHANNEL_PROJECT_ROOT — the absolute path to the project the daemon works with (e.g., C:\dev\projects\agent-studio). Task executors use this as their working directory for git, file, and code operations. If missing, defaults to the daemon's startup directory.TELEGRAM_ALLOWED_USERS — recommended (comma-separated user IDs)ANTHROPIC_API_KEY or CLAUDE_CODE_OAUTH_TOKEN — needed for headless monitor authRead ~/.claude/channels/telegram/access.json (path: C:\Users\oimir\.claude\channels\telegram\access.json). Check for:
allowFrom array with at least one user IDRead ~/.claude/channels/telegram/.env (path: C:\Users\oimir\.claude\channels\telegram\.env). Check for:
TELEGRAM_BOT_TOKEN presentRead .claude/.mcp.json. Check for:
telegram-relay key in mcpServersShow a simple checklist:
Telegram Setup Status:
[x] .env: Bot token configured
[x] .env: Owner ID: 6521653928
[x] .env: CHANNEL_AUTO_START=true
[x] .env: CHANNEL_PROJECT_ROOT=C:\dev\projects\agent-studio
[x] .env: Allowed users: 6521653928
[x] .env: Auth token configured (API key or OAuth token)
[x] Voice: transcribe-anything installed (pip)
[x] MCP: telegram-relay registered
[x] access.json: 1 allowed user
[x] channels/.env: token present
For any [ ] items, tell the user exactly what to add and where.
If both ANTHROPIC_API_KEY and CLAUDE_CODE_OAUTH_TOKEN are missing, tell the user:
! claude setup-token in your terminal, then add CLAUDE_CODE_OAUTH_TOKEN=<token> to .env"ANTHROPIC_API_KEY=sk-ant-... to .env (get one from console.anthropic.com)"If everything passes: "All configured! Run /enable-telegram to start monitoring."
Voice message support (optional): If the user wants voice messages to be transcribed, they need:
pip install transcribe-anything — Whisper-based speech-to-text (required for voice)ELEVENLABS_API_KEY or OPENAI_API_KEY in .env — for TTS audio responses (optional)transcribe-anything, voice messages get a "please type instead" fallback