How do I install the Fft Telegram Ops skill?

Run npx skillmds@latest add tomevault-io/fft-telegram-ops in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Fft Telegram Ops safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Fft Telegram Ops?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Fft Telegram Ops free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Fft Telegram Ops?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Fft Telegram Ops by tomevault-io — Agent Skill

Name: Fft Telegram Ops
Author: tomevault-io

File contents

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

Set host env:
- TELEGRAM_BOT_TOKEN=...
Optional for secure main claiming:
- TELEGRAM_ADMIN_SECRET=...
Recommended Telegram-only dev mode:
- WHATSAPP_ENABLED=0 ./scripts/start.sh dev telegram-only

Main Chat Setup

DM the bot and run /id.
Claim main chat:
- /main <secret> (requires TELEGRAM_ADMIN_SECRET)
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.

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.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: fft-telegram-opsdescription: Operate FFT_nano Telegram workflows including main chat claiming, command safety boundaries, admin panel usage, media intake behavior, and Telegram-first deployment patterns. Use when this capability is needed.---# FFT Telegram OpsUse 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 Telegram1. 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 Setup1. 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 PolicyAvailable 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.## 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.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/0-cyberdyne-systems-0) — claim your Tome and manage your conversions.

Frequently asked questions

Fft Telegram Ops