NanoClaw Container Debug
Diagnose NanoClaw's containerized agent runtime via its two SQLite session DBs and logs.
Test report
- Verdict
- Tested · Works
- Score
- Tested
- Jul 14, 2026
- Environment
- Claude Code 2.x (agent harness)
- Upstream re-checked
- Aug 10, 2026 · 0610ef8
Fed it a simulated '401 + container exits immediately' failure and it traced straight to the real cause via its own playbook — OneCLI selective secret mode — with the exact one-line fix (`onecli agents set-secret-mode --id <agent-id> --mode all`); a generic Docker-debugging pass has no way to know that command exists. The catch: every path, DB schema, and CLI name is specific to this one repo, so it's only useful if your project actually is NanoClaw.
Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works
- Installs cleanly 5/5
- Triggers reliably 4/5
- Output vs. baseline 8/10
- Docs & honesty 5/5
What NanoClaw Container Debug does
Walks through NanoClaw's host/container architecture (inbound.db / outbound.db message flow, mounts, OneCLI gateway secrets, heartbeat liveness) and lists four named failure modes with exact diagnostic commands. Triggers on generic phrasing ('container fails', 'authentication problems', 'things aren't working') but the entire body — file paths, image names, CLI (`ncl`), DB schemas — is hardcoded to the nanocoai/nanoclaw repo, so it only helps if that's the actual codebase.
How to install NanoClaw Container Debug
git clone https://github.com/nanocoai/nanoclaw
cd nanoclaw
mkdir -p ~/.claude/skills
cp -r .claude/skills/debug ~/.claude/skills/debug
Skills live in ~/.claude/skills/ (global) or .claude/skills/
(per-project). Restart Claude Code after installing.
Commands — how to trigger NanoClaw Container Debug
-
/debugDiagnose NanoClaw's containerized agent runtime via its two SQLite session DBs and logs.
It also activates on plain-language prompts like these:
-
Debug why my NanoClaw container exits immediately -
Diagnose the 401 error in my NanoClaw setup -
Fix the OneCLI secret mode breaking my container
Frequently asked questions
- Is the NanoClaw Container Debug skill free?
- Yes. The skill itself is free from nanocoai/nanoclaw. SkillProof publishes the install command and an independent test verdict at no cost.
- Does NanoClaw Container Debug work with Claude Code?
- We tested it with Claude Code 2.x (agent harness) on Jul 14, 2026. Verdict: Tested · Works. Fed it a simulated '401 + container exits immediately' failure and it traced straight to the real cause via its own playbook — OneCLI selective secret mode — with the exact one-line fix (`onecli agents set-secret-mode --id <agent-id> --mode all`); a generic Docker-debugging pass has no way to know that command exists. The catch: every path, DB schema, and CLI name is specific to this one repo, so it's only useful if your project actually is NanoClaw.
- What is the NanoClaw Container Debug SkillProof Score?
- 8.8/10 — installs cleanly 5/5, triggers reliably 4/5, output vs. baseline 8/10, docs & honesty 5/5.
- How do I install NanoClaw Container Debug?
- Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
- Can I use NanoClaw Container Debug with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
- The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.