OverviewHistoryStatsSecurity
npx skills add ...
Documentation
SKILL.md
npx skills add sentdm/sent-plugin --skill sent
Routes broad or ambiguous Sent requests to the correct MCP-backed operation or specialist skill. Use when the user asks what Sent can do, says "help me with Sent" or "set up messaging," needs several Sent workflows, or has not made the channel, task, or desired operation clear enough to select a more specific skill.
npx skills add sentdm/sent-plugin --skill sent
This skill is a router, not a worker. When a request does not identify one clear Sent workflow, inspect the intent, ask only the clarification needed to select a route, and invoke the matching skill.
Sent spans direct account operations through its MCP server and specialist guidance for SMS, WhatsApp, RCS, Sender Profiles, templates, and delivery analysis. Prefer a direct-operation skill for live Sent data or mutations and a specialist skill for planning, compliance, diagnosis, or product design.
Use when:
Do not use when:
https://docs.sent.dm or Sent support.| User intent | Target skill |
|---|---|
| Preview or send a templated message; inspect one message and its activity | sent-messaging |
| List, inspect, create, summarize, or delete Sent contacts | sent-contacts |
| Find, inspect, or delete existing Sent templates | sent-templates |
| Query dashboard messaging metrics or look up number capabilities | sent-analytics |
| Check the selected account, balance, onboarding state, or readiness to send | sent-account-readiness |
| User intent | Target skill |
|---|---|
| SMS compliance, 10DLC, brand or campaign registration, TCR vetting, or carrier rejects | sms-10dlc-registration |
| Authoring WhatsApp template content, choosing a category, or fixing a Meta rejection | waba-template-author |
| Connecting a WABA through Embedded Signup, callbacks, token exchange, or phone-number mapping | waba-embedded-signup |
| Launching RCS, preparing an RBM agent, or deciding capabilities and fallback | rcs-agent-onboarding |
| Designing multi-tenant Sender Profile boundaries, routing, or rate-limit ownership | sender-profile-architect |
| Diagnosing delivery from MDR exports, funnels, cohorts, or cross-channel failure codes | messaging-performance-analyzer |
| Designing or auditing a tenant-facing template-builder UI | template-builder-ui |
| User intent | Target skill |
|---|---|
| Adding Sent to a codebase, choosing an SDK, or hardening retries, idempotency, and error handling before launch | sent-integration-starter |
| Building or debugging a webhook receiver, signature verification, dedupe, or an auto-disabled endpoint | sent-webhook-engineer |
| Choosing the channel field, expecting cross-channel fallback, or interpreting a route, reroute, or delivery outcome | sent-routing-strategist |
| Handling inbound messages, opt-out keywords, consent state, the WhatsApp 24-hour window, or conversation history | sent-two-way-messaging |
| Executing the Sender Profile lifecycle over the API, including completion callbacks, campaigns, and user roles | sent-profile-provisioning |
| Replacing Twilio, Sinch, Infobip, Vonage, or Bird with Sent, including cutover and rollback planning | migrate-to-sent |
Within this group, note two frequent hand-offs: sender-profile-architect decides the tenancy boundary and sent-profile-provisioning implements it, while migrate-to-sent plans a provider replacement and sent-integration-starter hardens the resulting integration.
If the request matches one row cleanly, invoke that skill and stop. If it spans several rows, state the proposed order and begin with the prerequisite. For example, check sent-account-readiness before a live send, use sent-templates to locate an existing template before sent-messaging, and use messaging-performance-analyzer when the user provides an export rather than asking for live dashboard metrics.
Ask only what's needed to pick a lane. Stop as soon as the channel + workflow are unambiguous.
config_id?One question per turn is fine; never fire all seven at once.
This skill is not a fallback for general questions. If the user asks about:
sent-account-readiness.https://docs.sent.dm.sent-integration-starter once the question involves Sent's own retry, idempotency, or rate-limit contract.If after the clarifying questions the request still doesn't fit any target skill, say so plainly. Don't force a route.
Read references/sent-glossary.md when a routing decision depends on Sent, SMS, WhatsApp, RCS, or MCP terminology. Keep operational details in the target skill rather than duplicating them here.