Better Notify
better-notify/better-notify
End-to-end typed notification infrastructure for Node.js — typed catalog of email, SMS, push, web push, WhatsApp, Slack, Discord, Telegram, and GitHub notifications with provider-agnostic transports.
Set up the WhatsApp channel — configure the phone number, review access policy, and manage auth state.
Install Configure
$ npx skills add Rich627/whatsapp-claude-plugin --skill configure -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Rich627/whatsapp-claude-plugin configure --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/Rich627/whatsapp-claude-plugin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/configure .claude/skills/configure && 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 "configure" agent skill from https://github.com/Rich627/whatsapp-claude-plugin/tree/main/skills/configure into .claude/skills/configure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configure", 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/Rich627/whatsapp-claude-plugin/tree/main/skills/configureType 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 Rich627/whatsapp-claude-plugin --skill configure -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Rich627/whatsapp-claude-plugin configure --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Rich627/whatsapp-claude-plugin.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/configure .agents/skills/configure && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "configure" agent skill from https://github.com/Rich627/whatsapp-claude-plugin/tree/main/skills/configure into .agents/skills/configure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configure", 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 Rich627/whatsapp-claude-plugin --skill configure -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Rich627/whatsapp-claude-plugin configure --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Rich627/whatsapp-claude-plugin.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/configure .cursor/skills/configure && 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 "configure" agent skill from https://github.com/Rich627/whatsapp-claude-plugin/tree/main/skills/configure into .cursor/skills/configure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configure", 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/Rich627/whatsapp-claude-plugin.git --path skills/configure--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 Rich627/whatsapp-claude-plugin --skill configure -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Rich627/whatsapp-claude-plugin configure --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Rich627/whatsapp-claude-plugin.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/configure .gemini/skills/configure && 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 "configure" agent skill from https://github.com/Rich627/whatsapp-claude-plugin/tree/main/skills/configure into .gemini/skills/configure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configure", 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 Rich627/whatsapp-claude-plugin configureInstalls 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 Rich627/whatsapp-claude-plugin --skill configure -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Rich627/whatsapp-claude-plugin.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/configure .github/skills/configure && 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 "configure" agent skill from https://github.com/Rich627/whatsapp-claude-plugin/tree/main/skills/configure into .github/skills/configure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configure", 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 Rich627/whatsapp-claude-plugin --skill configure -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Rich627/whatsapp-claude-plugin configure --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Rich627/whatsapp-claude-plugin.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/configure .opencode/skills/configure && 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 "configure" agent skill from https://github.com/Rich627/whatsapp-claude-plugin/tree/main/skills/configure into .opencode/skills/configure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configure", 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.
Facts
- Skill name
configure- GitHub stars
- 101
- Token cost
- ~1.3k tokens
- SKILL.md length
- 641 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Set up the WhatsApp channel — configure the phone number, review access policy, and manage auth state.
- Works in 4 steps: Phone number — check… → Auth state — check whether… → Access — read… → …
- The user asks to configure WhatsApp
- SKILL.md covers Dispatch on arguments and Implementation notes
- Calls claude
What it does
Configure is an agent skill from Rich627/whatsapp-claude-plugin. Set up the WhatsApp channel — configure the phone number, review access policy, and manage auth state. Use when the user asks to configure WhatsApp, set a phone number, check channel status, or reset authentication.
Its SKILL.md is about 1.3k 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. It works with WhatsApp and Model Context Protocol. The repository describes itself as: Claude Code WhatsApp channel plugin — run AI directly from WhatsApp, voice transcription, remote tool approval, access control. No API keys, no Docker, just a linked device. The licence is Apache-2.0.
When your agent uses it
- The user asks to configure WhatsApp
- Set a phone number
- Check channel status
- Reset authentication
Example prompts
- “/configure”
Requirements
- Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(ls *), Bash(mkdir *), Bash(rm -rf *), Bash(chmod *), Read(~/.whatsapp-channel/*), Write(~/.whatsapp-channel/*), Edit(~/.whatsapp-channel/*)
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Phone number — check ~/.whatsapp-channel/.env for
- Auth state — check whether ~/.whatsapp-channel/.baileys_auth/creds.json
- Access — read ~/.whatsapp-channel/access.json (missing file
- What next — end with a concrete next step based on state
What it can do on your machine
Read from SKILL.md and the folder at commit 4274d5b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditBash(ls *)Bash(mkdir *)Bash(rm -rf *)Bash(chmod *)Read(~/.whatsapp-channel/*)Write(~/.whatsapp-channel/*)Edit(~/.whatsapp-channel/*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
claude
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Configure loads about 1.3k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 641 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.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:20
es configuration to `~/.whatsapp-channel/.env` and orients the - NoteMentions a .env fileSKILL.md:33
ne number** — check `~/.whatsapp-channel/.env` for - NoteMentions a .env fileSKILL.md:88
3. Read existing `.env` if present; update/add the `WHATSAPP_PHONE_NUMBER=` line, - NoteMentions a .env fileSKILL.md:90
4. `chmod 600 ~/.whatsapp-channel/.env` — the file may contain credentials. - NoteMentions a .env fileSKILL.md:112
- The server reads `.env` once at boot. Config changes need a session restart
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.
SKILL.md
The full file from Rich627/whatsapp-claude-plugin at commit 4274d5b, republished under its Apache-2.0 licence (© Rich627). 641 words, ~1,258 tokens.
Download SKILL.mdSave it as
.claude/skills/configure/SKILL.md (or your agent's skills folder).- name
- configure
- description
- Set up the WhatsApp channel — configure the phone number, review access policy, and manage auth state. Use when the user asks to configure WhatsApp, set a phone number, check channel status, or reset authentication.
- allowed-tools
- Read, Write, Edit, Bash(ls *), Bash(mkdir *), Bash(rm -rf *), Bash(chmod *), Read(~/.whatsapp-channel/*), Write(~/.whatsapp-channel/*), Edit(~/.whatsapp-channel/*)
- user-invocable
- true
/whatsapp-channel:configure — WhatsApp Channel Setup
Writes configuration to ~/.whatsapp-channel/.env and orients the
user on access policy. The server reads both files at boot.
Arguments passed: $ARGUMENTS
Dispatch on arguments
No args — status and guidance
Read both state files and give the user a complete picture:
Phone number — check
~/.whatsapp-channel/.envforWHATSAPP_PHONE_NUMBER. Show set/not-set; if set, show the number.Auth state — check whether
~/.whatsapp-channel/.baileys_auth/creds.jsonexists and hasregistered: true. Show paired/not-paired.Access — read
~/.whatsapp-channel/access.json(missing file = defaults:dmPolicy: "pairing", empty allowlist). Show:- DM policy and what it means in one line
- Allowed senders: count, and list JIDs
- Pending pairings: count, with codes and sender JIDs if any
What next — end with a concrete next step based on state:
- No phone number → "Run
/whatsapp-channel:configure <phone>with your WhatsApp phone number (e.g.886912345678, no leading +)." - Phone set but not paired → "Exit and launch with:
claude --dangerously-load-development-channels plugin:whatsapp-channel@whatsapp-claude-pluginThe pairing code will appear automatically. Enter it on your phone: WhatsApp > Linked Devices > Link a Device > Link with phone number instead." - Paired → "Ready. Your own number is auto-added to the allowlist.
To add others: have them DM the linked number, then approve with
/whatsapp-channel:access pair <code>."
- No phone number → "Run
Push toward lockdown — always. The goal for every setup is allowlist
with a defined list. pairing is not a policy to stay on; it's a temporary
way to capture WhatsApp JIDs you don't know. Once the JIDs are in, pairing
has done its job and should be turned off.
Drive the conversation this way:
- Read the allowlist. Tell the user who's in it.
- Ask: "Is that everyone who should reach you through this channel?"
- If yes and policy is still
pairing→ "Good. Let's lock it down so nobody else can trigger pairing codes:" and offer to run/whatsapp-channel:access policy allowlist. Do this proactively — don't wait to be asked. - If no, people are missing → "Have them DM the number; you'll approve
each with
/whatsapp-channel:access pair <code>. Run this skill again once everyone's in and we'll lock it." - If the allowlist is empty and they haven't paired themselves yet → "DM the linked number to capture your JID first. Then we'll add anyone else and lock it down."
- If policy is already
allowlist→ confirm this is the locked state. If they need to add someone: "They'll need to DM the linked number, or you can briefly flip to pairing:/whatsapp-channel:access policy pairing→ they DM → you pair → flip back."
Never frame pairing as the correct long-term choice. Don't skip the lockdown
offer.
Show full SKILL.md (223 more words)Show less
<phone> — save it
- Treat
$ARGUMENTSas the phone number (trim whitespace, strip leading+). WhatsApp phone numbers are digits only, no spaces or dashes. mkdir -p ~/.whatsapp-channel- Read existing
.envif present; update/add theWHATSAPP_PHONE_NUMBER=line, preserve other keys. Write back, no quotes around the value. chmod 600 ~/.whatsapp-channel/.env— the file may contain credentials.- Confirm, then show the no-args status so the user sees where they stand.
reset-auth
Clear the Baileys auth state so the user can re-pair with a new device or phone number.
- Confirm the user wants to do this — re-pairing will be required.
rm -rf ~/.whatsapp-channel/.baileys_auth- Inform: "Auth cleared. Restart your session with
--channelsto re-pair."
clear — remove the phone number
Delete the WHATSAPP_PHONE_NUMBER= line (or the file if that's the only line).
Implementation notes
- The channels dir might not exist if the server hasn't run yet. Missing file = not configured, not an error.
- The server reads
.envonce at boot. Config changes need a session restart or/reload-plugins. Say so after saving. access.jsonis re-read on every inbound message — policy changes via/whatsapp-channel:accesstake effect immediately, no restart.- WhatsApp uses linked-device protocol, not a bot API. The server connects as a linked device (like WhatsApp Web). Only one connection per auth state is allowed — running two instances causes a 440 conflict error.
© Rich627, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/configure of Rich627/whatsapp-claude-plugin.
Open the folder on GitHubat commit 4274d5b
Compare with similar skills
Configure 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 |
|---|---|---|---|---|---|---|
| Configure this skillRich627/whatsapp-claude-plugin | 101 | — | ~1.3k | Automated safety check: Notes | Apache-2.0 | |
| Better Notifybetter-notify/better-notify | 313 | — | ~783 | Automated safety check: Pass | MIT | |
| Frontmcp Channelsagentfront/frontmcp | 146 | — | ~3.7k | Automated safety check: Pass | Apache-2.0 | |
| Amazon Sesaws/agent-toolkit-for-aws | 2.8k | — | ~4k | Automated safety check: Pass | Apache-2.0 | |
| Add Gmailsbusso/claudeclaw | 194 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Agents Onboardingfazer-ai/agents | 118 | — | ~4.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Frontmcp Channels
agentfront/frontmcp
A skill your agent uses when pushing real-time notifications or events into Claude Code (or another MCP client) sessions, or building two-way chat bridges.
- Official
Amazon Ses
aws/agent-toolkit-for-aws
Guides Amazon SES onboarding for domain-based email sending.
Add Gmail
sbusso/claudeclaw
Add Gmail integration to ClaudeClaw. An agent skill from sbusso/claudeclaw.
Agents Onboarding
fazer-ai/agents
Conduz a jornada de onboarding 'do zero ao agente de atendimento' do fazer.ai agents num VPS, escolhendo o orquestrador de deploy (Tier A Coolify, B Portainer, C compose genérico para VM crua ou…
Ops Go
Lifecycle-Innovations-Limited/claude-ops
OPS on-demand: This skill should be used when the user asks to "morning briefing", "/ops:ops-go", or…
More from Rich627/whatsapp-claude-plugin
Access
Rich627/whatsapp-claude-plugin
WhatsApp channel access — approve pairings, edit allowlists, set DM/group policy.
Doctor
Rich627/whatsapp-claude-plugin
Diagnose WhatsApp channel problems — checks the server process, singleton lock, linked-device auth, access config, and optional features, then explains what's broken and how to fix it
Setup
Rich627/whatsapp-claude-plugin
Interactive WhatsApp channel onboarding — guides through device linking, phone number config, and access control setup
Related
Works with
Categories
Questions about Configure
What does Configure do?
Set up the WhatsApp channel — configure the phone number, review access policy, and manage auth state. Configure is an agent skill from Rich627/whatsapp-claude-plugin. Set up the WhatsApp channel — configure the phone number, review access policy, and manage auth state.
When should I use Configure?
Configure fits situations like: the user asks to configure WhatsApp; set a phone number; check channel status; reset authentication.
How do I install Configure in Claude Code?
Run `npx skills add Rich627/whatsapp-claude-plugin --skill configure -a claude-code`. Or copy the skill folder (skills/configure in Rich627/whatsapp-claude-plugin) into .claude/skills/configure in your project. Claude Code loads it when a task matches its description.
How do I install Configure in Codex?
Run `npx skills add Rich627/whatsapp-claude-plugin --skill configure -a codex`. Or copy the skill folder (skills/configure in Rich627/whatsapp-claude-plugin) into .agents/skills/configure in your project. Codex loads it when a task matches its description.
Can I use Configure in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Rich627/whatsapp-claude-plugin --skill configure -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/configure, .gemini/skills/configure, .github/skills/configure and .opencode/skills/configure in your project.
What does Configure need to run?
Going by SKILL.md and its folder, Configure needs the command-line tools its instructions call (claude). Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(ls *), Bash(mkdir *), Bash(rm -rf *), Bash(chmod *), Read(~/.whatsapp-channel/*), Write(~/.whatsapp-channel/*), Edit(~/.whatsapp-channel/*).
Does Configure access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Configure safe to install?
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.
What licence does Configure use?
Configure is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Configure use?
About 1.3k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Configure?
Skills that share tags, products or a category with Configure: Better Notify (better-notify/better-notify, 313 stars), Frontmcp Channels (agentfront/frontmcp, 146 stars), Amazon Ses (aws/agent-toolkit-for-aws, 2.8k stars) and Add Gmail (sbusso/claudeclaw, 194 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Configure?
Rich627 (a GitHub user) maintains it in Rich627/whatsapp-claude-plugin, which has 101 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 5, 2026.
Source: Rich627/whatsapp-claude-plugin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.