WhatsApp Business API

v1.0.0

Complete WhatsApp Business Cloud API for messages, templates, media, webhooks, flows, and business profiles.

0· 611·0 current·0 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The name/description and all curl examples target Meta's WhatsApp Business Cloud API and the required WHATSAPP_ACCESS_TOKEN and WHATSAPP_PHONE_NUMBER_ID are appropriate. The skill's declared purpose aligns with the operations described (messages, templates, media, webhooks, flows, business profiles).
!
Instruction Scope
SKILL.md and the auxiliary files instruct the agent to use additional environment variables (WHATSAPP_BUSINESS_ACCOUNT_ID and WHATSAPP_APP_SECRET), create and update a local memory file at ~/whatsapp-business-api/memory.md, and handle webhook verification. The registry metadata only declared two env variables (WHATSAPP_ACCESS_TOKEN and WHATSAPP_PHONE_NUMBER_ID) but the instructions use more — that's an incoherence because runtime behavior requires secrets not declared up front.
Install Mechanism
This is an instruction-only skill with no install spec and no bundled code, so nothing will be downloaded or written by an installer. That minimizes supply-chain risk.
!
Credentials
The declared primary credential (WHATSAPP_ACCESS_TOKEN) is appropriate. However, the documentation expects WHATSAPP_BUSINESS_ACCOUNT_ID and WHATSAPP_APP_SECRET (sensitive) for template management and webhook verification but these are not listed in requires.env. The missing declarations make it unclear what the platform will provide or request and whether those additional secrets would be exposed to the skill.
Persistence & Privilege
The skill stores preferences and memory under ~/whatsapp-business-api/memory.md (user home). Writing user-scoped files is expected for a conversational/integration helper and is not privileged, but anything stored there (phone numbers, webhook URLs, template names) could leak sensitive configuration if misused. The skill is not set to always:true and does not request system-wide changes.
What to consider before installing
This package appears to be a genuine WhatsApp Business Cloud API guide, but there are a few important mismatches to resolve before you install: - Confirm required credentials: The registry lists WHATSAPP_ACCESS_TOKEN and WHATSAPP_PHONE_NUMBER_ID, but the runtime docs also reference WHATSAPP_BUSINESS_ACCOUNT_ID and WHATSAPP_APP_SECRET (used for template operations and webhook signature verification). Ask the publisher or maintainer which env vars the platform will actually request and include those missing values in the declared requires.env if needed. - Protect secrets: Any access token or app secret you provide can be used to send messages or manage templates. Only provide the minimum-scoped token (system user or short-lived token as appropriate), rotate tokens regularly, and avoid pasting secrets into public chat/history. - Review local storage: The skill will create ~/whatsapp-business-api/memory.md and store context (phone numbers, webhook URLs, template references). Do not store secrets or tokens in that file. Review its contents periodically and restrict file permissions as needed. - Webhook handling: The skill correctly instructs verifying X-Hub-Signature-256 with the app secret; if you don’t supply WHATSAPP_APP_SECRET, webhook verification cannot be properly performed. Ensure your webhook verification is implemented server-side and that the secret is kept safe. - Autonomy considerations: The skill is invocable by the model (normal default). Because the skill can send API requests using your token, consider limiting autonomous invocation or approving actions interactively if you want tighter control over outgoing messages. - Source verification: The skill's homepage/source is listed as unknown; prefer skills from a known publisher or inspect any runtime hook if provided. Since this is instruction-only (no installer), risk is lower, but the mismatch in declared vs. used env vars is the main red flag. If you need to proceed: request the publisher update the registry metadata to list all env vars the skill will use (including WHATSAPP_APP_SECRET and WHATSAPP_BUSINESS_ACCOUNT_ID) and confirm exactly what the skill will store in ~/whatsapp-business-api/ before supplying credentials.

Like a lobster shell, security has layers — review code before you run it.

latestvk97b58bqqbvkvvyna7e5csvm1s81rf6m

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

💬 Clawdis
OSLinux · macOS · Windows
EnvWHATSAPP_ACCESS_TOKEN, WHATSAPP_PHONE_NUMBER_ID
Primary envWHATSAPP_ACCESS_TOKEN

Comments