# Customize

Add new capabilities or modify NanoClaw behavior.

- Repository: https://github.com/nanocoai/nanoclaw (31069 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add nanocoai/nanoclaw --skill customize -g -a claude-code -y`
Codex: `npx skills add nanocoai/nanoclaw --skill customize -g -a codex -y`
Cursor: `npx skills add nanocoai/nanoclaw --skill customize -g -a cursor -y`
Gemini CLI: `npx skills add nanocoai/nanoclaw --skill customize -g -a gemini-cli -y`

## Description

Add new capabilities or modify NanoClaw behavior. Use when user wants to add channels (Telegram, Slack, email input), change triggers, add integrations, modify the router, or make any other customizations. This is an interactive skill that asks questions to understand what the user wants.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# NanoClaw Customization

This skill helps users add capabilities or modify behavior. Use AskUserQuestion to understand what they want before making changes.

## Workflow

1. **Understand the request**, Ask clarifying questions.
2. **Prefer a dedicated skill**, If a skill covers the request, invoke it instead of editing core by hand:
   - Channels: `/add-telegram`, `/add-slack`, `/add-discord`, `/add-whatsapp`, `/add-signal`, `/add-imessage`, and the rest of the `/add-<channel>` family.
   - Wiring channels to agents and isolation levels: `/manage-channels`.
   - Container directory access: `/manage-mounts`.
   - Agent providers (non-default): `/add-opencode`, `/add-codex`, `/add-ollama-provider`.
   - MCP tools: `/add-ollama-tool`, `/add-atomic-chat-tool`.
3. **Plan the changes**, Identify the v2 surface the change belongs to (entity model in the central DB, per-agent-group container config, per-group `CLAUDE.md`, or core code).
4. **Implement**, Make the change on the right surface.
5. **Test guidance**, Tell the user how to verify.

## Entity Model

Customizations route through the v2 entity model: users → messaging groups → agent groups → sessions. A messaging group is one chat/channel on one platform; an agent group holds the workspace, personality, and container config; a wiring links a messaging group to an agent group with a session mode and trigger rules. Inspect and edit all of this with the `ncl` admin CLI. See `docs/isolation-model.md` for the three isolation levels.

## Key Files

The rest: https://github.com/nanocoai/nanoclaw/blob/HEAD/.claude/skills/customize/SKILL.md