nano-core-telegram-ops

name	nano-core-telegram-ops
description	Configure and operate nano-core through Telegram. Use for bot enablement, main/admin chat claims, trigger routing, command authorization, delivery modes, media intake, polling conflicts, and Telegram-first operation; not for WhatsApp-only or general runtime incidents.

nano-core Telegram Operations

Use current command specifications and runtime configuration. Before quoting a command matrix, read {baseDir}/references/commands.md.

When to use this skill

• Use for Telegram onboarding, main-chat assignment, trigger behavior, delivery settings, command scope, or media intake.
• Use for Telegram polling and authorization symptoms after basic runtime health is known.

When not to use this skill

• Do not use for WhatsApp-only workflows.
• Do not use for provider, container, database, or scheduler incidents unrelated to Telegram; use nano-core-debug.
• Do not bypass main/admin authorization or reveal an admin secret.

Workflow

1. Confirm TELEGRAM_BOT_TOKEN is configured without printing it. For Telegram-only operation, disable WhatsApp explicitly (WHATSAPP_ENABLED=0 or unset).
2. In a bot DM, use /id, then establish main/admin ownership with a configured TELEGRAM_MAIN_CHAT_ID or the /main <secret> claim flow (TELEGRAM_ADMIN_SECRET); if no main chat exists yet and the secret is unset, a direct DM can claim main with /main alone.
3. Verify /status. Use /gateway status (or /restart as its alias) for installed-service state when authorized.
4. Verify routing: main responds to every message; non-main chats require the message to start with the configured trigger (@<ASSISTANT_NAME>, default @nano-core, plus any ASSISTANT_ALIASES) unless free chat was explicitly enabled via /freechat.
5. Use /delivery or its alias /text_delivery to inspect or change Telegram text delivery mode (off|partial|block|draft|persistent). This controls Telegram response delivery, not scheduled-task delivery.
6. For media, verify TELEGRAM_MEDIA_MAX_MB and confirm the file lands under the group's inbox/telegram/ directory before claiming it is available to the agent.
7. For polling conflicts, identify and stop the duplicate process through the correct service manager; do not delete state.

Guardrails

• Never run destructive git commands unless explicitly requested.
• Preserve unrelated worktree changes.
• Telegram administration and coding delegation are main/admin chat only.
• Never send, log, or commit the bot token or admin secret.