菜单
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.
用 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.
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.
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.
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-setup |
| description | 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. |
Guide host installation and onboarding using the checkout's current README.md and docs/ONBOARDING.md as the source of truth.
nano-core-debug.npm install and npm run build../scripts/onboard-all.sh (backup -> setup -> onboarding wizard -> daemon step -> doctor), or nano-core onboard once the CLI is linked. Use its current --help output rather than inventing flags.CONTAINER_RUNTIME=auto selects it when available). Host runtime is an explicit, unisolated fallback requiring CONTAINER_RUNTIME=host plus NANO_CORE_ALLOW_HOST_RUNTIME=1 (and NANO_CORE_ALLOW_HOST_RUNTIME_IN_PROD=1 in production)..env at the repo root. Never print full keys or tokens.core is the default and always available. Install with npm run profile -- install <source>, activate with npm run profile -- activate <name>.nano-core doctor --json or npm run doctor, then inspect service status with nano-core service status or ./scripts/service.sh status.npm run backup:state (restore with npm run restore:state)..env, data/, groups/, the main workspace, and local customizations.