Moltflow Admin
LeoYeAI/openclaw-master-skills
Manage MoltFlow authentication, billing, API keys, usage tracking, and tenant settings.
Add WhatsApp as a channel. An agent skill from sbusso/claudeclaw.
$ npx skills add sbusso/claudeclaw --skill add-whatsapp -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sbusso/claudeclaw add-whatsapp --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sbusso/claudeclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/add-whatsapp .claude/skills/add-whatsapp && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "add-whatsapp" agent skill from https://github.com/sbusso/claudeclaw/tree/main/skills/add-whatsapp into .claude/skills/add-whatsapp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-whatsapp", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sbusso/claudeclaw/tree/main/skills/add-whatsappType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sbusso/claudeclaw --skill add-whatsapp -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sbusso/claudeclaw add-whatsapp --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sbusso/claudeclaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/add-whatsapp .agents/skills/add-whatsapp && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "add-whatsapp" agent skill from https://github.com/sbusso/claudeclaw/tree/main/skills/add-whatsapp into .agents/skills/add-whatsapp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-whatsapp", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sbusso/claudeclaw --skill add-whatsapp -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sbusso/claudeclaw add-whatsapp --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sbusso/claudeclaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/add-whatsapp .cursor/skills/add-whatsapp && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "add-whatsapp" agent skill from https://github.com/sbusso/claudeclaw/tree/main/skills/add-whatsapp into .cursor/skills/add-whatsapp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-whatsapp", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sbusso/claudeclaw.git --path skills/add-whatsapp--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sbusso/claudeclaw --skill add-whatsapp -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sbusso/claudeclaw add-whatsapp --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sbusso/claudeclaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/add-whatsapp .gemini/skills/add-whatsapp && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "add-whatsapp" agent skill from https://github.com/sbusso/claudeclaw/tree/main/skills/add-whatsapp into .gemini/skills/add-whatsapp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-whatsapp", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sbusso/claudeclaw add-whatsappInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sbusso/claudeclaw --skill add-whatsapp -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sbusso/claudeclaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/add-whatsapp .github/skills/add-whatsapp && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "add-whatsapp" agent skill from https://github.com/sbusso/claudeclaw/tree/main/skills/add-whatsapp into .github/skills/add-whatsapp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-whatsapp", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sbusso/claudeclaw --skill add-whatsapp -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sbusso/claudeclaw add-whatsapp --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sbusso/claudeclaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/add-whatsapp .opencode/skills/add-whatsapp && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "add-whatsapp" agent skill from https://github.com/sbusso/claudeclaw/tree/main/skills/add-whatsapp into .opencode/skills/add-whatsapp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-whatsapp", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
add-whatsappAdd WhatsApp as a channel. An agent skill from sbusso/claudeclaw.
Add Whatsapp is an agent skill from sbusso/claudeclaw. Add WhatsApp as a channel. Can replace other channels entirely or run alongside them. Uses QR code or pairing code for authentication.
Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Backend & APIs, covering Authentication. It works with WhatsApp. The repository describes itself as: Use Claude to orchestrate agents like OpenClaw. The licence is MIT.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 1395af4. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
npxnpmgitnodesqlite3bashFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
github.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Add Whatsapp loads about 2.9k tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 1,082 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
mkdir -p data/env && cp .env data/env/env3. Sync env: `mkdir -p data/env && cp .env data/env/env`Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from sbusso/claudeclaw at commit 1395af4, republished under its MIT licence (© sbusso). 1,082 words, ~2,851 tokens.
.claude/skills/add-whatsapp/SKILL.md (or your agent's skills folder).This skill adds WhatsApp support to ClaudeClaw. It installs the WhatsApp channel code, dependencies, and guides through authentication, registration, and configuration.
Check if WhatsApp is already configured. If store/auth/ exists with credential files, skip to Phase 4 (Registration) or Phase 5 (Verify).
ls store/auth/creds.json 2>/dev/null && echo "WhatsApp auth exists" || echo "No WhatsApp auth"Check whether the environment is headless (no display server):
[[ -z "$DISPLAY" && -z "$WAYLAND_DISPLAY" && "$OSTYPE" != darwin* ]] && echo "IS_HEADLESS=true" || echo "IS_HEADLESS=false"Use AskUserQuestion to collect configuration. Adapt auth options based on environment:
If IS_HEADLESS=true AND not WSL → AskUserQuestion: How do you want to authenticate WhatsApp?
Otherwise (macOS, desktop Linux, or WSL) → AskUserQuestion: How do you want to authenticate WhatsApp?
If they chose pairing code:
AskUserQuestion: What is your phone number? (Include country code without +, e.g., 1234567890)
Check if src/channels/whatsapp.ts already exists. If it does, skip to Phase 3 (Authentication).
git remote -vIf whatsapp is missing, add it:
git remote add whatsapp https://github.com/qwibitai/claudeclaw-whatsapp.gitgit fetch whatsapp main
git merge whatsapp/main || {
git checkout --theirs package-lock.json
git add package-lock.json
git merge --continue
}This merges in:
src/channels/whatsapp.ts (WhatsAppChannel class with self-registration via registerChannel)src/channels/whatsapp.test.ts (41 unit tests)src/channels/whatsapp-auth.ts (standalone WhatsApp authentication script)setup/whatsapp-auth.ts (WhatsApp auth setup step)import './whatsapp.js' appended to the channel barrel file src/channels/index.ts'whatsapp-auth' step added to setup/index.ts@whiskeysockets/baileys, qrcode, qrcode-terminal npm dependencies in package.jsonASSISTANT_HAS_OWN_NUMBER in .env.exampleIf the merge reports conflicts, resolve them by reading the conflicted files and understanding the intent of both sides.
npm install
npm run build
npx vitest run src/channels/whatsapp.test.tsAll tests must pass and build must be clean before proceeding.
rm -rf store/auth/For QR code in browser (recommended):
npx tsx setup/index.ts --step whatsapp-auth -- --method qr-browser(Bash timeout: 150000ms)
Tell the user:
A browser window will open with a QR code.
- Open WhatsApp > Settings > Linked Devices > Link a Device
- Scan the QR code in the browser
- The page will show "Authenticated!" when done
For QR code in terminal:
npx tsx setup/index.ts --step whatsapp-auth -- --method qr-terminalTell the user to run npm run auth in another terminal, then:
- Open WhatsApp > Settings > Linked Devices > Link a Device
- Scan the QR code displayed in the terminal
For pairing code:
Tell the user to have WhatsApp open on Settings > Linked Devices > Link a Device, ready to tap "Link with phone number instead" — the code expires in ~60 seconds and must be entered immediately.
Run the auth process in the background and poll store/pairing-code.txt for the code:
rm -f store/pairing-code.txt && npx tsx setup/index.ts --step whatsapp-auth -- --method pairing-code --phone <their-phone-number> > /tmp/wa-auth.log 2>&1 &Then immediately poll for the code (do NOT wait for the background command to finish):
for i in $(seq 1 20); do [ -f store/pairing-code.txt ] && cat store/pairing-code.txt && break; sleep 1; doneDisplay the code to the user the moment it appears. Tell them:
Enter this code now — it expires in ~60 seconds.
- Open WhatsApp > Settings > Linked Devices > Link a Device
- Tap Link with phone number instead
- Enter the code immediately
After the user enters the code, poll for authentication to complete:
for i in $(seq 1 60); do grep -q 'AUTH_STATUS: authenticated' /tmp/wa-auth.log 2>/dev/null && echo "authenticated" && break; grep -q 'AUTH_STATUS: failed' /tmp/wa-auth.log 2>/dev/null && echo "failed" && break; sleep 2; doneIf failed: qr_timeout → re-run. logged_out → delete store/auth/ and re-run. 515 → re-run. timeout → ask user, offer retry.
test -f store/auth/creds.json && echo "Authentication successful" || echo "Authentication failed"Channels auto-enable when their credentials are present — WhatsApp activates when store/auth/creds.json exists.
Sync to container environment:
mkdir -p data/env && cp .env data/env/envGet the bot's WhatsApp number: node -e "const c=require('./store/auth/creds.json');console.log(c.me.id.split(':')[0].split('@')[0])"
AskUserQuestion: Is this a shared phone number (personal WhatsApp) or a dedicated number (separate device)?
AskUserQuestion: What trigger word should activate the assistant?
AskUserQuestion: What should the assistant call itself?
AskUserQuestion: Where do you want to chat with the assistant?
Shared number options:
Dedicated number options:
Self-chat: JID = your phone number with @s.whatsapp.net. Extract from auth credentials:
node -e "const c=JSON.parse(require('fs').readFileSync('store/auth/creds.json','utf-8'));console.log(c.me?.id?.split(':')[0]+'@s.whatsapp.net')"DM with bot: Ask for the bot's phone number. JID = NUMBER@s.whatsapp.net
Group (solo, existing): Run group sync and list available groups:
npx tsx setup/index.ts --step groups
npx tsx setup/index.ts --step groups --listThe output shows JID|GroupName pairs. Present candidates as AskUserQuestion (names only, not JIDs).
npx tsx setup/index.ts --step register \
--jid "<jid>" \
--name "<chat-name>" \
--trigger "@<trigger>" \
--folder "whatsapp_main" \
--channel whatsapp \
--assistant-name "<name>" \
--is-main \
--no-trigger-required # Only for main/self-chatFor additional groups (trigger-required):
npx tsx setup/index.ts --step register \
--jid "<group-jid>" \
--name "<group-name>" \
--trigger "@<trigger>" \
--folder "whatsapp_<group-name>" \
--channel whatsappnpm run buildService name: Derived from the directory name:
com.claudeclaw.<dirname>(macOS) /claudeclaw-<dirname>(Linux). For example, if cwd ismy-assistant, the service iscom.claudeclaw.my-assistant. Determine the correct service name before running service commands below.
Restart the service:
# macOS (launchd)
launchctl kickstart -k gui/$(id -u)/com.claudeclaw
# Linux (systemd)
systemctl --user restart claudeclaw
# Linux (nohup fallback)
bash start-claudeclaw.shTell the user:
Send a message to your registered WhatsApp chat:
- For self-chat / main: Any message works
- For groups: Use the trigger word (e.g., "@Andy hello")
The assistant should respond within a few seconds.
tail -f logs/claudeclaw.logQR codes expire after ~60 seconds. Re-run the auth command:
rm -rf store/auth/ && npx tsx src/channels/whatsapp-auth.tsCodes expire in ~60 seconds. To retry:
rm -rf store/auth/ && npx tsx src/channels/whatsapp-auth.ts --pairing-code --phone <phone>Enter the code immediately when it appears. Also ensure:
+ (e.g., 1234567890)If pairing code keeps failing, switch to QR-browser auth instead:
rm -rf store/auth/ && npx tsx setup/index.ts --step whatsapp-auth -- --method qr-browserThis happens when two instances connect with the same credentials. Ensure only one ClaudeClaw process is running:
pkill -f "node dist/service.js"
# Then restartCheck:
ls store/auth/creds.jsonsqlite3 store/messages.db "SELECT * FROM registered_groups WHERE jid LIKE '%whatsapp%' OR jid LIKE '%@g.us' OR jid LIKE '%@s.whatsapp.net'"launchctl list | grep claudeclaw (macOS) or systemctl --user status claudeclaw (Linux)tail -50 logs/claudeclaw.logRun group metadata sync:
npx tsx setup/index.ts --step groupsThis fetches all group names from WhatsApp. Runs automatically every 24 hours.
If running npm run dev while the service is active:
# macOS:
launchctl unload ~/Library/LaunchAgents/com.claudeclaw.plist
npm run dev
# When done testing:
launchctl load ~/Library/LaunchAgents/com.claudeclaw.plist
# Linux:
# systemctl --user stop claudeclaw
# npm run dev
# systemctl --user start claudeclawTo remove WhatsApp integration:
rm -rf store/auth/sqlite3 store/messages.db "DELETE FROM registered_groups WHERE jid LIKE '%@g.us' OR jid LIKE '%@s.whatsapp.net'"mkdir -p data/env && cp .env data/env/envnpm run build && launchctl kickstart -k gui/$(id -u)/com.claudeclaw (macOS) or npm run build && systemctl --user restart claudeclaw (Linux)© sbusso, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/add-whatsapp of sbusso/claudeclaw.
Open the folder on GitHubat commit 1395af4
Add Whatsapp next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Add Whatsapp this skillsbusso/claudeclaw | 194 | — | ~2.9k | Automated safety check: Notes | MIT | |
| Moltflow AdminLeoYeAI/openclaw-master-skills | 2.2k | — | ~2.5k | Automated safety check: Pass | MIT | |
| Fortify Developmentcoollabsio/coolify | 63k | 4 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Supabase Development and Debuggingsupabase/agent-skills | 2.7k | 3 repos | ~3.6k | Automated safety check: Pass | MIT | |
| Better Auth Best Practiceslatitude-dev/latitude-llm | 4.7k | 7 repos | ~1.6k | Automated safety check: Pass | MIT | |
| Gitnexus Exploringaws-samples/sample-kolya-br-proxy | 106 | 12 repos | ~749 | Automated safety check: Pass | MIT-0 |
LeoYeAI/openclaw-master-skills
Manage MoltFlow authentication, billing, API keys, usage tracking, and tenant settings.
coollabsio/coolify
ACTIVATE when the user works on authentication in Laravel. An agent skill from coollabsio/coolify.
supabase/agent-skills
General Supabase skill for database, auth, Edge Functions, Realtime and storage work, plus client libraries, migrations, security audits, debugging and reading logs.
latitude-dev/latitude-llm
Configure Better Auth server and client, set up database adapters, manage sessions, add plugins, and handle environment variables.
aws-samples/sample-kolya-br-proxy
A skill your agent uses when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase.
curvenote/curvenote
A skill your agent uses when doing ANY task involving Supabase.
sbusso/claudeclaw
Debug container agent issues. An agent skill from sbusso/claudeclaw.
sbusso/claudeclaw
X (Twitter) integration for ClaudeClaw. An agent skill from sbusso/claudeclaw.
sbusso/claudeclaw
Add Gmail integration to ClaudeClaw. An agent skill from sbusso/claudeclaw.
sbusso/claudeclaw
Add QMD (Query Markup Documents) as an advanced memory search backend.
sbusso/claudeclaw
Add Telegram as a channel. An agent skill from sbusso/claudeclaw.
sbusso/claudeclaw
Add Agent Swarm (Teams) support to Telegram. An agent skill from sbusso/claudeclaw.
Works with
Categories
Add WhatsApp as a channel. An agent skill from sbusso/claudeclaw. Add Whatsapp is an agent skill from sbusso/claudeclaw. Add WhatsApp as a channel.
Add Whatsapp fits situations like: tasks that involve Authentication.
Run `npx skills add sbusso/claudeclaw --skill add-whatsapp -a claude-code`. Or copy the skill folder (skills/add-whatsapp in sbusso/claudeclaw) into .claude/skills/add-whatsapp in your project. Claude Code loads it when a task matches its description.
Run `npx skills add sbusso/claudeclaw --skill add-whatsapp -a codex`. Or copy the skill folder (skills/add-whatsapp in sbusso/claudeclaw) into .agents/skills/add-whatsapp in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sbusso/claudeclaw --skill add-whatsapp -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/add-whatsapp, .gemini/skills/add-whatsapp, .github/skills/add-whatsapp and .opencode/skills/add-whatsapp in your project.
Going by SKILL.md and its folder, Add Whatsapp needs the command-line tools its instructions call (npx, npm, git, node, sqlite3 and bash). Our summary lists: Node.js.
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Add Whatsapp is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.9k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Add Whatsapp: Moltflow Admin (LeoYeAI/openclaw-master-skills, 2.2k stars), Fortify Development (coollabsio/coolify, 63k stars), Supabase Development and Debugging (supabase/agent-skills, 2.7k stars) and Better Auth Best Practices (latitude-dev/latitude-llm, 4.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
sbusso (a GitHub user) maintains it in sbusso/claudeclaw, which has 194 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on August 12, 2026.
Source: sbusso/claudeclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.