customize

Modify NanoClaw TypeScript channel modules and orchestration for new integrations.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/wientjes/gforce-nanoclaw --skill customize-wientjes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: customize
Source: https://github.com/wientjes/gforce-nanoclaw/tree/main/.claude/skills/customize
Command: npx skills add https://github.com/wientjes/gforce-nanoclaw --skill customize-wientjes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides users through adding or modifying NanoClaw capabilities so they can safely extend input channels, integrations, triggers, and routing without guessing which files to change. It reduces the friction and risk of ad-hoc edits by asking clarifying questions, outlining necessary code changes, and explaining how to test and deploy updates.

Core Features & Use Cases

  • Interactive scoping: Ask targeted questions to decide channel type, trigger patterns, memory separation, and group routing before touching code.
  • Implementation patterns: Provides concrete file targets and patterns for adding channels (src/channels/*.ts), wiring instances in src/index.ts, updating personas in groups/CLAUDE.md, and mounting MCP integrations.
  • Use Case: Add Telegram as an input channel, decide whether it shares conversation context with WhatsApp, implement src/channels/telegram.ts, wire it into main, and verify authentication and routing.

Quick Start

Ask the customize skill to add Telegram as an input channel and answer its configuration and routing questions.

Frequently Asked Questions about customize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new Telegram channel to a TypeScript bot deployment?

Adding a Telegram channel involves implementing src/channels/telegram.ts, wiring the instance in src/index.ts, updating group personas, and rebuilding and restarting the service to apply routing changes.

What is the best way to route messages to different personas in a multi-channel bot?

Adjusting message routing requires updating group persona files like groups/CLAUDE.md and modifying src/index.ts orchestration to ensure triggers from specific channels direct to the correct persona configurations.

Can I mount MCP integrations and adjust triggers without breaking existing channels?

Yes, you can mount MCP integrations and adjust triggers safely by using interactive scoping to decide trigger configurations and memory separation before modifying TypeScript channel modules and rebuilding the service.

Do I need to edit src/index.ts to wire a Slack input channel?

Yes, wiring a Slack input channel requires editing src/index.ts orchestration to mount the new channel instance alongside updating the corresponding TypeScript channel module and rebuilding the deployment.

Why does my customized bot channel share conversation context with other channels?

Customized bot channels share conversation context when memory separation is not explicitly configured during setup, requiring adjustments to TypeScript channel modules and orchestration to isolate conversation state.

When should I not use ad-hoc edits for adding email integrations?

You should avoid ad-hoc edits for adding email integrations when modifying triggers or routing, as guessing which TypeScript files to change introduces deployment risk and friction without proper interactive scoping.