菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Map of the Tailscale network (tailnet) and how to reach, operate, and deploy to remote machines over it via SSH. Use for any cross-machine task — remote install, deploy, restart, log-check, or file transfer.
Operate nano-core coding delegation. Use for /coder or /coding execution, /coder-plan or /coder_plan planning, natural-language coding approval prompts, delegated runs, run IDs, progress, cancellation, and final-result handling; not for direct coding or automatic delegation.
Diagnose nano-core runtime failures. Use for provider/model errors, Pi launch or skill-discovery failures, Telegram/WhatsApp routing, singleton locks, service state, IPC, SQLite state, scheduler behavior, or per-group logs; not for installation or feature work.
Install or onboard nano-core on a host. Use for first-time installation, prerequisites, runtime selection, provider/channel configuration, daemon setup, upgrades, or doctor checks; not for diagnosing an already-running incident.
Understand and operate nano-core itself. Use for questions about nano-core architecture, behavior, configuration, capabilities, skills, installation, troubleshooting, Telegram administration, or coding delegation; route focused work to the matching nano-core skill.
Set up and run an autonomous experiment loop for any optimization target. Gathers what to optimize, then starts the loop immediately. Use when asked to "run autoresearch", "optimize X in a loop", "set up autoresearch for X", or "start experiments".
| 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. |
Use current command specifications and runtime configuration. Before quoting a command matrix, read {baseDir}/references/commands.md.
nano-core-debug.TELEGRAM_BOT_TOKEN is configured without printing it. For Telegram-only operation, disable WhatsApp explicitly (WHATSAPP_ENABLED=0 or unset)./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./status. Use /gateway status (or /restart as its alias) for installed-service state when authorized.@<ASSISTANT_NAME>, default @nano-core, plus any ASSISTANT_ALIASES) unless free chat was explicitly enabled via /freechat./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.TELEGRAM_MEDIA_MAX_MB and confirm the file lands under the group's inbox/telegram/ directory before claiming it is available to the agent.