messenger
✓Verified·Scanned 2/17/2026
This skill provides Messenger Platform guidance for sending messages, handling webhooks, and managing Page messaging. It instructs outbound HTTPS calls to https://graph.facebook.com (e.g., POST /me/messages, GET /me/accounts) and the use of Page/User access tokens; this behavior is purpose-aligned.
from clawhub.ai·vd05c0f7·5.3 KB·0 installs
Scanned from 1.0.1 at d05c0f7 · Transparency log ↗
$ vett add clawhub.ai/codedao12/messenger
Facebook Messenger API Skill (Advanced)
Purpose
Provide a production-oriented guide for Messenger Platform workflows: sending messages, handling webhooks, and managing Page messaging using direct HTTPS calls.
Best fit
- You need bot-style messaging in Facebook Messenger.
- You want clean webhook handling and message UX.
- You prefer direct HTTP requests rather than SDKs.
Not a fit
- You need advanced Graph API Ads or Marketing workflows.
- You must use complex browser-based OAuth flows.
Quick orientation
- Read
references/messenger-api-overview.mdfor base URLs and core object map. - Read
references/webhooks.mdfor verification and signature validation. - Read
references/messaging.mdfor Send API fields and message types. - Read
references/permissions-and-tokens.mdfor token flow and required permissions. - Read
references/request-templates.mdfor concrete HTTP payloads. - Read
references/conversation-patterns.mdfor UX flows (get started, menu, fallback). - Read
references/webhook-event-map.mdfor event types and routing.
Required inputs
- Facebook App ID and App Secret.
- Page ID and Page access token.
- Webhook URL and verify token.
- Message UX and allowed interactions.
Expected output
- A clear messaging workflow plan, permissions checklist, and operational guardrails.
Operational notes
- Validate signatures on all webhook events.
- Keep replies short and acknowledge quickly.
- Handle rate limits and retries with backoff.
Security notes
- Never log tokens or app secrets.
- Use least-privilege permissions.