fft-telegram-ops

DevOps Community

Repo stars 0
Author repo nano-core

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Operate FFT_nano Telegram workflows including main chat claiming, command safety boundaries, admin panel usage, media intake beh…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “When to use this skill”, “When not to use this skill”, “Guardrails”, “Enable Telegram”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name fft-telegram-ops directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “When to use this skill / When not to use this skill / Guardrails” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

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

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: 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
Author / version / license: @0-CYBERDYNE-SYSTEMS-0 · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Plug-and-play
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Write / modify
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview fft-telegram-ops.preview

The current SKILL.md does not define a fixed output example.

SKILL.md 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.

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

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 -> TELEGRAMBOTTOKEN=... · TELEGRAMADMINSECRET=... · WHATSAPPENABLED=0 ./scripts/start.sh dev telegram-only · /id · /main <secret> · TELEGRAMADMINSECRET · TELEGRAMMAINCHATID · /help
body sha256 -> 171b77425b96