Sent Meta Dispatcher

Overview

This skill is a router, not a worker. It exists so that when a user mentions Sent without naming a specific channel or workflow, Claude inspects the request, asks the smallest number of clarifying questions needed to pick a lane, and then invokes the correct vertical skill — instead of guessing, doing partial work in the wrong vertical, or paraphrasing skill content here.

Sent is a unified messaging platform spanning SMS (10DLC / TCR in the US), WhatsApp (WABA via Meta), and RCS (RBM via Google). Each channel has its own onboarding, compliance, content rules, and failure modes; conflating them produces bad advice. The seven vertical skills in this plugin each own one slice of that surface area. This skill's only job is to put the user in front of the right one quickly.

When to Use

Use when:

• The user mentions "Sent" broadly without naming a channel ("help me with Sent", "I want to use Sent for messaging")
• The user asks an open-ended question like "what can you help with on Sent?" or "where do I start?"
• The request could plausibly span multiple vertical skills (e.g., "messaging isn't working" — could be 10DLC vetting, WABA template rejection, RBM capability, or MDR funnel)
• The channel is ambiguous (SMS vs WhatsApp vs RCS not stated; geography matters because 10DLC is US-only)
• The surface is ambiguous (API integration vs dashboard UX vs compliance paperwork)
• The user pastes a Sent dashboard URL or API path without further context