电报操作

运维部署 社区

技能解读

当前原文的自动摘译,尚未人工审校。

何时使用该技能

在 FFT_nano 中设置或修复 Telegram 机器人路由时使用。在声明/维护主聊天和管理命令边界时使用。在验证 Telegram 媒体摄入量和命令策略行为时使用。

什么时候不应该使用这个技能

请勿用于仅限 WhatsApp 的流程。请勿用于与 Telegram 路由无关的非聊天后端设置任务。不要用于绕过特权命令的主/管理限制。

护栏

除非明确要求,否则切勿运行破坏性的 git 命令。保留不相关的工作树更改。对于管理/委托操作,仅强制执行主聊天是强制性的。

启用电报

设置主机环境:TELEGRAM_BOT_TOKEN=...安全主声明可选:TELEGRAM_ADMIN_SECRET=...推荐的仅 Telegram 开发模式:

主要聊天设置

DM 机器人并运行/id。声明主聊天:/main <secret>(需要TELEGRAM_ADMIN_SECRET)替代方案:设置TELEGRAM_MAIN_CHAT_ID并重新启动。

流狐档案 运行与权限由流狐静态检查推断,不代表作者声明或实际测试结果。
领域
运维部署
作者声明的智能体
未找到明确声明;不据此推断已兼容或已测试
静态检查
88 / 100 · 启发式扫描,不代表运行安全
运行环境证据
未执行;当前没有隔离运行测试证据
作者 / 版本 / 许可证
@0-CYBERDYNE-SYSTEMS-0 · 未声明许可证
上下文用量评级
低消耗
接入复杂程度
即装即用
是否需要外部接口密钥
不需要
兼容的系统
未声明(默认跨平台)
运行环境要求
未检出明确要求
检测到的文件与系统行为
  • 只读
  • 允许写入 / 修改
网络行为
仅限本地
安装命令数
无(仅作为资料)

需要注意: 未声明工具权限范围;实际权限由运行环境决定。

作者说明文件(原文) SKILL.md

# 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.

讨论

基于 GitHub Discussions。登录 GitHub 即可参与讨论、点赞、订阅更新。