What problem does it solve? Modifying a self-hosted assistant like NanoClaw requires knowing which surface to change — the central entity database, per-agent-group container configs, per-group CLAUDE.md files, or core TypeScript code. This Skill removes that guesswork by asking clarifying questions and routing each customization request to the right dedicated skill, CLI command, or file. ## Core Features & Use Cases - Interactive scoping: Uses clarifying questions to understand what the user wants before making any changes, then plans against the v2 entity model (users, messaging groups, agent groups, wirings). - Channel and integration routing: Directs channel additions (Telegram, Slack, Discord, WhatsApp, Signal, email) to the matching /add-<channel> install skills and MCP integrations (Gmail, Google Calendar, Ollama) to /add-<service>-tool skills. - Behavior and deployment changes: Covers persona edits in groups/<folder>/CLAUDE.md, container config updates via the ncl admin CLI, trigger rule changes on wirings, and launchd/systemd deployment adjustments. - Use Case: A user says "Add Telegram as an input channel." The Skill runs /add-telegram to install the adapter, asks which agent group and isolation level to use, then wires the messaging group to the agent group with a session mode and trigger rules. ## Quick Start Ask the assistant to add a new channel, integration, or behavior change to NanoClaw and answer its clarifying questions about agent groups and isolation levels.