一键导入
convert-to-docker
Normalize nano-core to Docker-first runtime defaults. Use when user asks for Docker parity, cross-platform setup, or to disable host runtime mode.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Normalize nano-core to Docker-first runtime defaults. Use when user asks for Docker parity, cross-platform setup, or to disable host runtime mode.
用 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.
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.
| name | convert-to-docker |
| description | Normalize nano-core to Docker-first runtime defaults. Use when user asks for Docker parity, cross-platform setup, or to disable host runtime mode. |
| disable-model-invocation | true |
This repository now supports two runtime modes:
docker (preferred/default)host (advanced, explicit opt-in)This skill enforces Docker-first configuration and verifies the runtime end-to-end.
docker --version
docker info >/dev/null && echo "Docker ready" || echo "Docker not ready"
If Docker is missing:
curl -fsSL https://get.docker.com | sh && sudo systemctl start dockerUpdate .env so Docker is selected and host-mode overrides are removed:
# ensure runtime is docker-first auto mode
if grep -q '^CONTAINER_RUNTIME=' .env 2>/dev/null; then
sed -i.bak 's/^CONTAINER_RUNTIME=.*/CONTAINER_RUNTIME=auto/' .env
else
echo 'CONTAINER_RUNTIME=auto' >> .env
fi
# remove host runtime opt-ins if present
sed -i.bak '/^NANO_CORE_ALLOW_HOST_RUNTIME=/d' .env
sed -i.bak '/^NANO_CORE_ALLOW_HOST_RUNTIME_IN_PROD=/d' .env
./container/build.sh
npm run build
echo '{}' | docker run -i --entrypoint /bin/echo nano-core-agent:latest "Container OK"
Run the project setup checker (Docker path):
bash scripts/setup.sh
Expected behavior:
launchctl kickstart -k gui/$(id -u)/com.nano-core
CONTAINER_RUNTIME=host unless explicitly requested.NANO_CORE_ALLOW_HOST_RUNTIME=1.