customize
Extend ClaudeClaw with new input channels, adjust routing rules, and personalize agent responses. This interactive skill guides you through adding Telegram, Slack, Discord, email, or other integrations, then helps rebuild and restart your setup.
Customize skill lets you add input channels like Telegram or Slack, modify ClaudeClaw triggers, and extend agent behavior.
AI-generated summary based on this skill's SKILL.md
Install
sbusso/claudeclaw/customize · repository language: TypeScript
git clone https://github.com/sbusso/claudeclaw
cp -r claudeclaw/skills/customize ~/.claude/skills/customizeFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I add Telegram to ClaudeClaw?
ClaudeClaw supports adding Telegram as an input channel through its customization framework. To add Telegram, you'll need to configure a new channel in your ClaudeClaw instance by setting up the Telegram bot credentials and routing rules. The skill guides you through obtaining your bot token, configuring the input handler, and rebuilding your deployment so messages from Telegram flow to your assistant with the routing behavior you define.
How can I customize ClaudeClaw behavior and triggers?
ClaudeClaw's customization skill lets you modify assistant behavior, persona, triggers, and response patterns. You can adjust how your agent responds to different inputs, change trigger words that activate specific behaviors, and personalize the assistant's tone and communication style. The skill walks you through editing configuration files, testing your changes locally, and redeploying to apply your customizations across all active channels.
Can I add Slack, Discord, or email channels to my assistant?
Yes, ClaudeClaw enables adding multiple input channels including Slack, Discord, and email. The customize skill provides step-by-step guidance for each platform: connecting your Slack workspace, registering a Discord bot, or configuring email forwarding. Once configured, messages from any channel route through your ClaudeClaw instance according to rules you define, allowing unified assistant management across platforms.
How do I migrate from plugin mode to developer mode?
ClaudeClaw's customization skill supports migrating from plugin mode to developer mode for full customization control. This transition lets you fork your configuration, access underlying code, and make advanced modifications beyond the plugin interface. The skill guides you through exporting your current setup, setting up a development environment, and rebuilding your instance in developer mode with all your existing channels and behaviors preserved.
How can I add new MCP integrations or custom commands?
ClaudeClaw allows integrating new MCP services and adding custom commands through its customization framework. The skill helps you identify compatible MCP providers, configure service credentials, and define custom command handlers that extend your assistant's capabilities. You can then rebuild and restart your deployment to activate the new integrations and make custom commands available across your configured input channels.
What's included in the ClaudeClaw customization guide?
ClaudeClaw's customization skill is a comprehensive guide covering channel integration, behavior modification, and deployment configuration. It addresses adding input channels like Telegram and Slack, adjusting routing rules and triggers, personalizing assistant responses, migrating to developer mode, and integrating MCP services. The skill provides hands-on walkthroughs for each customization task, then helps you rebuild and restart your setup to apply changes.
SKILL.md
rendered from the published skill — quoted content, verbatim
ClaudeClaw Customization
This skill helps users add capabilities or modify behavior. Use AskUserQuestion to understand what they want before making changes.
Mode Detection
Check if .claude-plugin/plugin.json exists in cwd:
cat .claude-plugin/plugin.json 2>/dev/null | grep '"name": "claudeclaw"' && echo "DEVELOPER_MODE" || echo "PLUGIN_MODE"
If plugin mode, offer the user a choice via AskUserQuestion: - Fork to developer mode (Recommended) — Clone the repo into a new directory, copy state, full self-improvement and customization - Continue in plugin mode — Limited to channel setup and config changes (no code editing)
If "Fork to developer mode" is chosen, run the migration flow below. Otherwise, proceed with the normal workflow (limited to invoking existing skills like /add-slack, /add-telegram).
Migration: Plugin →
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
skills/customize/SKILL.md