customize
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.
Best use case
customize is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using customize should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/customize/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How customize Compares
| Feature / Agent | customize | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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. **Plan the changes** - Identify files to modify 3. **Implement** - Make changes directly to the code 4. **Test guidance** - Tell user how to verify ## Key Files | File | Purpose | |------|---------| | `src/config.ts` | Assistant name, trigger pattern, directories | | `src/index.ts` | Message routing, WhatsApp connection, agent invocation | | `src/db.ts` | Database initialization and queries | | `src/types.ts` | TypeScript interfaces | | `src/whatsapp-auth.ts` | Standalone WhatsApp authentication script | | `.mcp.json` | MCP server configuration (reference) | | `groups/CLAUDE.md` | Global memory/persona | ## Common Customization Patterns ### Adding a New Input Channel (e.g., Telegram, Slack, Email) Questions to ask: - Which channel? (Telegram, Slack, Discord, email, SMS, etc.) - Same trigger word or different? - Same memory hierarchy or separate? - Should messages from this channel go to existing groups or new ones? Implementation pattern: 1. Find/add MCP server for the channel 2. Add connection and message handling in `src/index.ts` 3. Store messages in the database (update `src/db.ts` if needed) 4. Ensure responses route back to correct channel ### Adding a New MCP Integration Questions to ask: - What service? (Calendar, Notion, database, etc.) - What operations needed? (read, write, both) - Which groups should have access? Implementation: 1. Add MCP server to the `mcpServers` config in `src/index.ts` 2. Add tools to `allowedTools` array 3. Document in `groups/CLAUDE.md` ### Changing Assistant Behavior Questions to ask: - What aspect? (name, trigger, persona, response style) - Apply to all groups or specific ones? Simple changes → edit `src/config.ts` Persona changes → edit `groups/CLAUDE.md` Per-group behavior → edit specific group's `CLAUDE.md` ### Adding New Commands Questions to ask: - What should the command do? - Available in all groups or main only? - Does it need new MCP tools? Implementation: 1. Add command handling in `processMessage()` in `src/index.ts` 2. Check for the command before the trigger pattern check ### Changing Deployment Questions to ask: - Target platform? (Linux server, Docker, different Mac) - Service manager? (systemd, Docker, supervisord) Implementation: 1. Create appropriate service files 2. Update paths in config 3. Provide setup instructions ## After Changes Always tell the user: ```bash # Rebuild and restart npm run build launchctl unload ~/Library/LaunchAgents/com.nanoclaw.plist launchctl load ~/Library/LaunchAgents/com.nanoclaw.plist ``` ## Example Interaction User: "Add Telegram as an input channel" 1. Ask: "Should Telegram use the same @Andy trigger, or a different one?" 2. Ask: "Should Telegram messages create separate conversation contexts, or share with WhatsApp groups?" 3. Find Telegram MCP or library 4. Add connection handling in index.ts 5. Update message storage in db.ts 6. Tell user how to authenticate and test
Related Skills
setup
Run initial NanoClaw setup. Use when user wants to install dependencies, authenticate WhatsApp, register their main channel, or start the background services. Triggers on "setup", "install", "configure nanoclaw", or first-time setup requests.
setup-linux
Set up NanoClaw on Linux (Ubuntu/Debian recommended). Installs deps, configures .env, optional WhatsApp auth, and optional systemd service.
debug
Debug container agent issues. Use when things aren't working, container fails, authentication problems, or to understand how the container system works. Covers logs, environment variables, mounts, and common issues.
add-gmail
Add Gmail integration to NanoClaw. Can be configured as a tool (agent reads/sends emails when triggered from WhatsApp) or as a full channel (emails can trigger the agent, schedule tasks, and receive replies). Guides through GCP OAuth setup and implements the integration.
add-discord
Enable Discord as a NanoClaw channel (works alongside WhatsApp or Discord-only).
/add-codex
Add Codex CLI as an alternative NanoClaw agent runtime.
cowork-plugin-customizer
Customize a Claude Code plugin for a specific organization's tools and workflows. Use when: customize plugin, set up plugin, configure plugin, tailor plugin, adjust plugin settings, customize plugin connectors, customize plugin skill, tweak plugin, modify plugin configuration.
customize
Interactive guided deployment flow for Azure OpenAI models with full customization control. Step-by-step selection of model version, SKU (GlobalStandard/Standard/ProvisionedManaged), capacity, RAI policy (content filter), and advanced options (dynamic quota, priority processing, spillover). USE FOR: custom deployment, customize model deployment, choose version, select SKU, set capacity, configure content filter, RAI policy, deployment options, detailed deployment, advanced deployment, PTU deployment, provisioned throughput. DO NOT USE FOR: quick deployment to optimal region (use preset).
customize
Interactive guided deployment flow for Azure OpenAI models with full customization control. Step-by-step selection of model version, SKU (GlobalStandard/Standard/ProvisionedManaged), capacity, RAI policy (content filter), and advanced options (dynamic quota, priority processing, spillover). USE FOR: custom deployment, customize model deployment, choose version, select SKU, set capacity, configure content filter, RAI policy, deployment options, detailed deployment, advanced deployment, PTU deployment, provisioned throughput. DO NOT USE FOR: quick deployment to optimal region (use preset).
customize-upstream-sync
Pull the latest upstream AIWG updates into the user's fork and rebuild — preserves user customizations
customize-status
Show current AIWG customization status — mode, source path, what you've customized vs upstream
customize-setup
Set up personal AIWG customization mode from a local clone or fork — makes your clone the live global AIWG instance so edits go live immediately