customize
Add new capabilities or modify MicroClaw 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 MicroClaw 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 MicroClaw 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
# MicroClaw 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.microclaw.plist launchctl load ~/Library/LaunchAgents/com.microclaw.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
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
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.
debug-validator-checkpoint-inconsistency
Debug validator checkpoint inconsistencies where some validators are behind others. Use when alerts mention "checkpoint inconsistency", "validators behind", or "inconsistent latest checkpoints", or when asked to debug validator sets, investigate validator delays, or troubleshoot metadata fetch failures for a chain. Defaults to default_ism app context if not specified.
debug-log-patterns
Language-specific debug logging patterns and best practices. Reference when adding instrumentation for Dart/Flutter, Kotlin/Android, Swift/iOS, or JavaScript/TypeScript applications.
debug-detective
Systematic debugging approach for ANY codebase, ANY language, ANY bug type. Use when facing unexpected behavior, crashes, performance issues, or intermittent problems.
debug:angular
Debug Angular applications systematically with expert-level diagnostic techniques. This skill provides comprehensive guidance for troubleshooting dependency injection errors, change detection issues (NG0100), RxJS subscription leaks, lazy loading failures, zone.js problems, and common Angular runtime errors. Includes structured four-phase debugging methodology, Angular DevTools usage, console debugging utilities (ng.probe), and performance profiling strategies for modern Angular applications.
De-novo-motif-discovery
This skill identifies novel transcription factor binding motifs in the promoter regions of genes, or directly from genomic regions of interest such as ChIP-seq peaks, ATAC-seq accessible sites, or differentially acessible regions. It employs HOMER (Hypergeometric Optimization of Motif Enrichment) to detect both known and previously uncharacterized sequence motifs enriched within the supplied genomic intervals. Use the skill when you need to uncover sequence motifs enriched or want to know which TFs might regulate the target regions.
ddd-tactical-patterns
Apply DDD tactical patterns in code using entities, value objects, aggregates, repositories, and domain events with explicit invariants.
ddd-context-mapping
Map relationships between bounded contexts and define integration contracts using DDD context mapping patterns.
dd-logs
Log management - search, pipelines, archives, and cost control.
dd-apm
APM - traces, services, dependencies, performance analysis.
dcg
Destructive Command Guard - High-performance Rust hook for Claude Code that blocks dangerous commands before execution. SIMD-accelerated, modular pack system, whitelist-first architecture. Essential safety layer for agent workflows.