fft-telegram-ops
Skill4 starsChanged 8 months agoMITView on GitHub
Operate FFT_nano Telegram workflows including main chat claiming, command safety boundaries, admin panel usage, media intake behavior, and Telegram-first deployment patterns.
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-telegramSkill
- add-telegram-swarmSkill
- agent-browserSkill
- agent-harness-engineerSkill
- autoresearch-createSkill
- autoresearch-finalizeSkill
- fft-coder-opsSkill
- fft-dashboard-opsSkill
- fft-debugSkill
- fft-farm-bootstrapSkill
- fft-farm-onboardingSkill
- fft-farm-opsSkill
- fft-host-ipcSkill
- fft-setupSkill
- loopsSkill
- rapid-researchSkill
- skill-mechanicSkill
- web-searchSkill
- customizeSkill
- debugSkill
- setupSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 7 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill for Telegram onboarding, operations, and safe admin command handling.
- Very specific: line 12
Use when setting up or repairing Telegram bot routing in FFT_nano.
- Distinctive: line 13
Use when claiming/maintaining main chat and admin command boundaries.
- Distinctive: line 14
Use when verifying Telegram media intake and command policy behavior.
- Distinctive: line 18
Do not use for WhatsApp-only flows.
- Distinctive: line 19
Do not use for non-chat backend setup tasks unrelated to Telegram routing.
- Distinctive: line 20
Do not use to bypass main/admin restrictions for privileged commands.
- Distinctive: line 24
Never run destructive git commands unless explicitly requested.
- Very specific: line 87
Run /status in Telegram to confirm runtime and channel state.
- Very specific: line 88
Use /panel in main chat for task/group/coder quick actions.
- Very specific: line 89
If polling conflicts occur, stop duplicate FFT_nano instances.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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>(requiresTELEGRAM_ADMIN_SECRET)
- Alternative: set
TELEGRAM_MAIN_CHAT_IDand 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 [status|stream|append|off|draft]controls Telegram text preview behavior for the current chat (defaultstatus: milestones + final summary). It is not cron delivery./text_deliveryis an alias for/delivery.streamis the default durable preview message/edit mode.appendsends durable in-flight update blocks that remain in chat; the final answer is sent separately.offdisables preview streaming and sends only the final answer.draftuses Telegram nativesendMessageDraftfor 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
/statusin Telegram to confirm runtime and channel state. - Use
/panelin main chat for task/group/coder quick actions. - If polling conflicts occur, stop duplicate FFT_nano instances.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

