configure
Skill0 starsChanged 7 months agoMITView on GitHub
This skill should be used when the user wants to "configure WhatsApp", "set up WhatsApp", "save a phone number ID", "save an access token", "check WhatsApp credential status", "update the API version", "clear WhatsApp credentials", or says "/meta-configure".
- Reads credentials
43 other projects use a version of this.
Adopted by
Most recently taken up by
- jskswamy/skillstheir own version, first seen Nov 8, 2026
- btrazzini/hippOStheir own version, first seen Nov 8, 2026
- CodesWhat/careerrattheir own version, first seen Nov 3, 2026
- Totes-MickGOATs/opus-pocustheir own version, first seen Nov 1, 2026
- Edmonds-Commerce-Limited/claude-code-hooks-daemontheir own version, first seen Oct 28, 2026
- talal-ai/handoff-nowtheir own version, first seen Oct 20, 2026
Used with
Projects with it also use calendar, setup and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
jacobraskSkillcalendar
Interact with Apple Calendar via AppleScript. Use when the user asks to check calendar, view events, create events, manage schedule, find free time, or list calendars. Triggers include "my calendar", "my schedule", "calendar events", "create event", "add to calendar", "what's on my calendar", "free time", "available slots", "upcoming events", "today's events". Requires macOS with Calendar.app.
Also in 3 projects that use this
VercelSkillsetup
Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".
Also in 7 projects that use this
AnthropicSkillstatus
Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.
Also in 3 projects that use this
Microsoft AzureSkillbuild
Build the TypeSpec Rust emitter from source. Run this after cloning the repo, after pulling changes, or when TypeScript source files have been modified.
Also in 3 projects that use this
Other versions43 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 43
- anthropics/claude-plugins-official★ 46ksame name
- bitwize-music-studio/claude-ai-music-skills★ 589same name
- m1heng/claude-plugin-weixin★ 564same name
- fw-ai/cookbook★ 241same name
- k1p1l0/claude-telegram-supercharged★ 144same name
- Rich627/whatsapp-claude-plugin★ 114same name
- paceaitian/cc-wechat★ 68same name
- jeremylongshore/claude-code-slack-channel★ 43same name
- atomicinnovation/accelerator★ 34same name
- spotify/ads-agentic-tools★ 20same name
33 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repositoryOne other file it gives its agents.
- sendSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 5 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 43 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 33
Read ~/.claude/channels/whatsapp/.env and display:
- Distinctive: line 39
Follow with a next-step hint:
- Distinctive: line 40
If not configured: *"Run the configure skill with your Phone Number ID and Access Token to get started."*
- Distinctive: line 41
If configured: *"Ready. Ask me to send a WhatsApp message anytime."*
- Very specific: line 48
Read existing .env if present, or start with an empty string.
- Distinctive: line 49
Update or add these three lines (preserve any other keys already in the file):
- Distinctive: line 55
Write the file back.
- Very specific: line 63
Update META_WA_API_VERSION in the .env file to the provided value (e.g., v19.0).
- Very specific: line 70
Remove the .env file entirely, or — if the file contains other keys beyond the three WhatsApp keys — remove only those three keys and leave …
- Very specific: line 82
Never print the full access token.
“Common” is measured: kept by at least 6 in 10 of the 43 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Manage Meta WhatsApp Business API credentials stored in ~/.claude/channels/whatsapp/.env.
The .env file holds three keys:
META_WA_PHONE_NUMBER_ID=<value>
META_WA_ACCESS_TOKEN=<value>
META_WA_API_VERSION=v18.0Determine the user's intent from their message and dispatch to the matching action below.
Action: Status (no args, or "status")
Read ~/.claude/channels/whatsapp/.env and display:
- Phone Number ID — full value, or "not set"
- Access Token — first 10 characters +
..., or "not set" - API Version — current value, or "default: v18.0"
Follow with a next-step hint:
- If not configured: "Run the configure skill with your Phone Number ID and Access Token to get started."
- If configured: "Ready. Ask me to send a WhatsApp message anytime."
Action: Save credentials (<phone_number_id> <access_token>)
- Run
mkdir -p ~/.claude/channels/whatsapp - Read existing
.envif present, or start with an empty string. - Update or add these three lines (preserve any other keys already in the file):
META_WA_PHONE_NUMBER_ID=<phone_number_id> META_WA_ACCESS_TOKEN=<access_token> META_WA_API_VERSION=v18.0 - Write the file back.
- Run
chmod 600 ~/.claude/channels/whatsapp/.env - Confirm success, then show status (as above).
Action: Update API version (version <version_string>)
Update META_WA_API_VERSION in the .env file to the provided value (e.g., v19.0).
Confirm the change.
Action: Clear credentials (clear)
Remove the .env file entirely, or — if the file contains other keys beyond the three WhatsApp keys — remove only those three keys and leave the rest intact.
Confirm to the user that credentials have been cleared.
Credential reference
Obtain credentials from Meta for Developers → your WhatsApp Business app → API Setup:
- Phone Number ID — numeric string shown under your test or production phone number
- Access Token — temporary (24 h) or permanent system-user token
Never print the full access token; always mask it as the first 10 characters + ....
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.