fft telegram ops
- Repo stars 0
- Author repo nano-core
- Domain
- DevOps
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @0-CYBERDYNE-SYSTEMS-0 · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# FFT Telegram Ops
Use this skill for Telegram onboarding, operations, and safe admin command handling.
## When to use this skill
- Use when setting up or repairing Telegram bot routing in FFT_nano.
- Use when claiming/maintaining main chat and admin command boundaries.
- Use when verifying Telegram media intake and command policy behavior.
## When not to use this skill
- Do not use for WhatsApp-only flows.
- Do not use for non-chat backend setup tasks unrelated to Telegram routing.
- Do not use to bypass main/admin restrictions for privileged commands.
## Guardrails
- Never run destructive git commands unless explicitly requested.
- Preserve unrelated worktree changes.
- Main-chat-only enforcement is mandatory for admin/delegation operations.
## Enable Telegram
1. Set host env:
- `TELEGRAM_BOT_TOKEN=...`
2. Optional for secure main claiming:
- `TELEGRAM_ADMIN_SECRET=...`
3. Recommended Telegram-only dev mode:
- `WHATSAPP_ENABLED=0 ./scripts/start.sh dev telegram-only`
## Main Chat Setup
1. DM the bot and run `/id`.
2. Claim main chat:
- `/main <secret>` (requires `TELEGRAM_ADMIN_SECRET`)
3. Alternative: set `TELEGRAM_MAIN_CHAT_ID` and restart.
## Command Policy
Available everywhere:
- `/help`
- `/status`
- `/id`
Main/admin chat only:
- `/main <secret>`
- `/tasks`
- `/task_pause <id>`
- `/task_resume <id>`
- `/task_cancel <id>`
- `/groups`
- `/reload`
- `/panel`
- `/coder <task>`
- `/coder-plan <task>`
## Messaging Behavior
- Main chat responds to all messages.
- Non-main chats require trigger prefix `@<ASSISTANT_NAME>` (default `@FarmFriend`).
- Coder delegation is rejected in non-main chats.
- `/delivery [stream|append|off|draft]` controls Telegram text preview behavior for the current chat. It is not cron delivery.
- `/text_delivery` is an alias for `/delivery`.
- `stream` is the default durable preview message/edit mode.
- `append` sends durable in-flight update blocks that remain in chat; the final answer is sent separately.
- `off` disables preview streaming and sends only the final answer.
- `draft` uses Telegram native `sendMessageDraft` for ephemeral in-flight previews; the final answer is still sent as a normal durable message.
## Media Intake
- Telegram uploads are persisted under:
- `groups/<group>/inbox/telegram/`
- Agent sees uploaded files as:
- `/workspace/group/inbox/telegram/...`
- Size limit controlled by `TELEGRAM_MEDIA_MAX_MB`.
## Operational Checks
- Run `/status` in Telegram to confirm runtime and channel state.
- Use `/panel` in main chat for task/group/coder quick actions.
- If polling conflicts occur, stop duplicate FFT_nano instances.
Sections and files
Listed in source order.
sections -> When to use this skill → When not to use this skill → Guardrails → Enable Telegram → Main Chat Setup → Command Policy
terms -> Use this skill for Telegram onboarding, operations, and safe admin command handling. · - Use when setting up or repairing Telegram bot routing in FFTnano. · - Do not use for WhatsApp-only flows. · - Never run destructive git commands unless explicitly requested. · 1. Set host env: - TELEGRAMBOTTOKEN=... · 1. DM the bot and run /id. · - Main chat responds to all messages. · - Run /status in Telegram to confirm runtime and channel state.
files/cmd -> TELEGRAM_BOT_TOKEN=... · TELEGRAM_ADMIN_SECRET=... · WHATSAPP_ENABLED=0 ./scripts/start.sh dev telegram-only · /id · /main <secret> · TELEGRAM_ADMIN_SECRET · TELEGRAM_MAIN_CHAT_ID · /help
body sha256 -> 171b77425b96
When to use this skill
Use when setting up or repairing Telegram bot routing in FFT_nano. Use when claiming/maintaining main chat and admin command boundaries. Use when verifying Telegram media intake and command policy behavior.
When not to use this skill
Do not use for WhatsApp-only flows. Do not use for non-chat backend setup tasks unrelated to Telegram routing. Do not use to bypass main/admin restrictions for privileged commands.
Guardrails
Never run destructive git commands unless explicitly requested. Preserve unrelated worktree changes. Main-chat-only enforcement is mandatory for admin/delegation operations.
Enable Telegram
Set host env:
TELEGRAM_BOT_TOKEN=...Optional for secure main claiming:TELEGRAM_ADMIN_SECRET=...Recommended Telegram-only dev mode:Main Chat Setup
DM the bot and run
/id. Claim main chat:/main <secret>(requiresTELEGRAM_ADMIN_SECRET) Alternative: setTELEGRAM_MAIN_CHAT_IDand restart.