skill111WhatsApp Business API integration with managed OAuth. Send messages, manage templates, and handle conversations. Use this skill when users want to interact w...
Install via ClawdBot CLI:
clawdbot install kenhee350-a11y/skill111Grade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Sends data to undocumented external endpoint (potential exfiltration)
Send → https://developers.facebook.com/docs/whatsapp/cloud-api/guides/send-messagesCalls external URL not in known-safe list
https://clawhub.ai/byungkyu/api-gatewayUses known external API (expected, informational)
discord.comAudited Apr 17, 2026 · audit v1.0
Generated Mar 22, 2026
Businesses can use this skill to automate responses to common customer inquiries on WhatsApp, such as order status updates or FAQ answers. It integrates with existing support systems to provide 24/7 assistance, reducing response times and improving customer satisfaction.
Healthcare clinics or service-based businesses can send automated appointment reminders and confirmations via WhatsApp messages. This reduces no-shows by engaging patients directly on a widely used platform, streamlining scheduling processes.
Companies can leverage pre-approved WhatsApp message templates to run marketing campaigns, such as promotional offers or event notifications. This allows for personalized outreach at scale while complying with WhatsApp's business messaging policies.
Logistics and delivery services can send real-time updates on order status, shipping notifications, and delivery confirmations through WhatsApp. This enhances transparency and customer engagement by providing timely information via a familiar channel.
Offer this skill as part of a subscription-based service where businesses pay a monthly fee for access to WhatsApp Business API integration. Revenue is generated through tiered pricing based on message volume or features like advanced analytics.
Charge businesses based on the number of messages sent or API calls made through the skill. This model suits companies with fluctuating messaging needs, allowing them to scale costs according to usage without long-term commitments.
License the skill to other platforms or developers who can rebrand and integrate it into their own applications. Revenue comes from licensing fees or revenue-sharing agreements, expanding reach through partnerships.
💬 Integration Tip
Ensure the MATON_API_KEY is securely stored as an environment variable and test connection management endpoints before sending messages to avoid authentication issues.
Scored Jun 19, 2026
Self-hosted auth for TypeScript/Cloudflare Workers with social auth, 2FA, passkeys, organizations, RBAC, and 15+ plugins. Requires Drizzle ORM or Kysely for D1 (no direct adapter). Self-hosted alternative to Clerk/Auth.js. Use when: self-hosting auth on D1, building OAuth provider, multi-tenant SaaS, or troubleshooting D1 adapter errors, session caching, rate limits, Expo crashes, additionalFields bugs.
Clerk integration. Manage Users, Organizations. Use when the user wants to interact with Clerk data.
Clerk auth with API Keys beta (Dec 2025), Next.js 16 proxy.ts (March 2025 CVE context), API version 2025-11-10 breaking changes, clerkMiddleware() options, webhooks, production considerations (GCP outages), and component reference. Prevents 15 documented errors. Use when: API keys for users/orgs, Next.js 16 middleware filename, troubleshooting JWKS/CSRF/JWT/token-type-mismatch errors, webhook verification, user type inconsistencies, or testing with 424242 OTP.
Host static files on subdomains with optional authentication. Use when you need to serve HTML, images, CSS, JS, or any static content on a dedicated subdomain. Supports file upload, basic auth, quota management, and automatic SSL via Caddy. Commands include sf sites (create/list/delete), sf upload (files/directories), sf files (list/delete).
Use the botauth CLI to list, search, and retrieve secrets from the user's unlocked botauth vault with per-request approval in the desktop app. Use when a tas...
Use when adding, fixing, or improving how an app authenticates users or protects an API, or when using or configuring any Auth0 feature — signing users in and out, sessions and tokens, guarding routes and endpoints, MFA, SSO, Organizations, RBAC, custom domains, Universal Portals for hosted account