Whatsapp business workflow
Plan and validate official WhatsApp Business messaging integrations, including onboarding, webhooks, conversation policy, templates, consent, and provider boundaries.From its SKILL.md
npx -y skills add gaelic-ghost/socket --skill whatsapp-business-workflowAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, 222 tokens by cl100k_base, as published. Nobody here has run it
WhatsApp Business Workflow
Workflow
- Confirm the current official WhatsApp Business Platform path or the chosen approved provider before implementation. Record who owns the business account, phone number, webhook, and credentials.
- Recheck current Meta policy for user opt-in, template approval, conversation windows, message categories, and regional restrictions. These rules are release-sensitive and must not be copied from memory.
- Verify webhook authenticity, deduplicate status/message events, and separate inbound message handling from delivery/read-status processing.
- Treat a WhatsApp phone identity, application account, user consent, template, and conversation window as explicit data inputs.
- Design opt-out, human escalation, media retention, and failure fallback before adding AI-generated replies.
- Validate with an approved test environment, observed webhook signatures, template state, inbound/outbound behavior, delivery status, and stop/escalation paths.
Provider Boundary
An approved CPaaS provider can simplify transport but does not remove WhatsApp business policy obligations. Keep provider-specific types and credentials at the provider boundary; do not convert this skill into a universal WhatsApp client.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.