Awesome-omni-skill 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.

install

source · Clone the upstream repo

git clone https://github.com/diegosouzapw/awesome-omni-skill

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/development/customize" ~/.claude/skills/diegosouzapw-awesome-omni-skill-customize && rm -rf "$T"

manifest: skills/development/customize/SKILL.md

source content

MicroClaw Customization

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

Workflow

Understand the request - Ask clarifying questions
Plan the changes - Identify files to modify
Implement - Make changes directly to the code
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:

Find/add MCP server for the channel
Add connection and message handling in
```
src/index.ts
```
Store messages in the database (update
```
src/db.ts
```
if needed)
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:

Add MCP server to the
```
mcpServers
```
config in
```
src/index.ts
```
Add tools to
```
allowedTools
```
array
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:

Add command handling in
```
processMessage()
```
in
```
src/index.ts
```
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:

Create appropriate service files
Update paths in config
Provide setup instructions

After Changes

Always tell the user:

# 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"

Ask: "Should Telegram use the same @Andy trigger, or a different one?"
Ask: "Should Telegram messages create separate conversation contexts, or share with WhatsApp groups?"
Find Telegram MCP or library
Add connection handling in index.ts
Update message storage in db.ts
Tell user how to authenticate and test