sentdm · sent-dm · Aug 10, 2026 · Aug 10, 2026
diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.json
@@ -5,14 +5,14 @@
     "url": "https://sent.dm"
   },
   "metadata": {
-    "description": "Official Sent skills and remote MCP integration for messaging operations and specialist channel workflows.",
+    "description": "Official Sent skills and remote MCP integration for messaging engineering, operations, migration, and specialist channel workflows.",
     "version": "0.1.0"
   },
   "plugins": [
     {
       "name": "sent",
       "source": "./claude-plugins/sent",
-      "description": "Official Sent business messaging plugin for safe SMS, WhatsApp, RCS, contacts, templates, analytics, account readiness, delivery diagnosis, 10DLC, WABA, RBM, and Sender Profile workflows.",
+      "description": "Official Sent business messaging plugin for SMS, WhatsApp, RCS, API integration, webhooks, routing, two-way messaging, Sender Profiles, migration, compliance, analytics, and agent-safe operations.",
       "category": "Productivity"
     }
   ]

diff --git a/README.md b/README.md
@@ -75,9 +75,17 @@ The repository root is directly discoverable as an Agent Plugins 1.0.0 package.
 | `rcs-agent-onboarding` | Prepare an RCS Business Messaging agent, carrier-approval evidence, capabilities, SMS fallback, and launch checks | “onboard an RBM agent”, “RCS carrier approval”, “design SMS fallback” | [`skills/rcs-agent-onboarding/SKILL.md`](skills/rcs-agent-onboarding/SKILL.md) |
 | `sender-profile-architect` | Design multi-tenant and multi-brand Sender Profile boundaries, webhook routing, lifecycle, and channel ownership | “model 50 messaging tenants”, “profile per brand?”, “route webhooks by tenant” | [`skills/sender-profile-architect/SKILL.md`](skills/sender-profile-architect/SKILL.md) |
 | `template-builder-ui` | Design or audit a tenant-facing SMS, WhatsApp, and RCS template editor and submission workflow | “build a WhatsApp template editor”, “design template validation”, “handle approval states” | [`skills/template-builder-ui/SKILL.md`](skills/template-builder-ui/SKILL.md) |
+| `sent-integration-starter` | Stand up and harden a Sent v3 integration: SDK choice, idempotent sends, retry policy, error families, launch checklist | “add Sent to our app”, “what retry policy?”, “are we production ready?” | [`skills/sent-integration-starter/SKILL.md`](skills/sent-integration-starter/SKILL.md) |
+| `sent-webhook-engineer` | Build and debug webhook receivers: signature verification, replay window, dedupe, retries, auto-disable recovery | “401 on every webhook”, “verify the signature header”, “our endpoint went inactive” | [`skills/sent-webhook-engineer/SKILL.md`](skills/sent-webhook-engineer/SKILL.md) |
+| `sent-routing-strategist` | Choose channels and diagnose routes: broadcast versus automatic routing, reroute behavior, and delivery outcomes | “RCS then SMS fallback?”, “why is channel auto?”, “recipients got two messages” | [`skills/sent-routing-strategist/SKILL.md`](skills/sent-routing-strategist/SKILL.md) |
+| `sent-two-way-messaging` | Design inbound flows: keyword consent, opt-out state, the WhatsApp 24-hour window, RCS STOP chips, conversation history | “do I handle STOP myself?”, “auto-reply stopped working”, “page conversation history” | [`skills/sent-two-way-messaging/SKILL.md`](skills/sent-two-way-messaging/SKILL.md) |
+| `sent-profile-provisioning` | Execute the Sender Profile lifecycle: create, inheritance, completion callback, campaigns, users and roles | “create a profile via the API”, “completion callback never arrived”, “invite a developer” | [`skills/sent-profile-provisioning/SKILL.md`](skills/sent-profile-provisioning/SKILL.md) |
+| `migrate-to-sent` | Migrate from Twilio, Sinch, Infobip, Vonage, or Bird: concept mapping, dual-run, staged cutover, rollback | “moving off Sinch”, “Vonage failover equivalent”, “dual-run comparison metrics” | [`skills/migrate-to-sent/SKILL.md`](skills/migrate-to-sent/SKILL.md) |
 
 Use `sent-analytics` for aggregate dashboard totals and trends. Use `messaging-performance-analyzer` for message-level evidence, funnel drop-off, and root-cause analysis. Use `sent-templates` for existing records, `waba-template-author` for WhatsApp content and policy decisions, and `template-builder-ui` for product UX.
 
+For engineering work, use `sent-integration-starter` to stand up and harden a new integration, `sent-webhook-engineer` for receiver construction and delivery debugging, `sent-routing-strategist` for channel selection and route diagnosis, `sent-two-way-messaging` for inbound and consent flows, `sent-profile-provisioning` to execute the profile lifecycle that `sender-profile-architect` designs, and `migrate-to-sent` when replacing an incumbent provider.
+
 ## Live MCP capabilities
 
 The plugin declares the Streamable HTTP endpoint `https://mcp.sent.dm/mcp` and exposes these operations through the authorized connection:

diff --git a/adapter-sources/shared/README.md b/adapter-sources/shared/README.md
@@ -19,6 +19,12 @@ This generated host adapter packages the official Sent Agent Skills and remote M
 | `rcs-agent-onboarding` | Prepare an RBM agent for approval and launch | [`skills/rcs-agent-onboarding/SKILL.md`](skills/rcs-agent-onboarding/SKILL.md) |
 | `sender-profile-architect` | Design multi-tenant Sender Profile architecture | [`skills/sender-profile-architect/SKILL.md`](skills/sender-profile-architect/SKILL.md) |
 | `template-builder-ui` | Design cross-channel template-builder UX | [`skills/template-builder-ui/SKILL.md`](skills/template-builder-ui/SKILL.md) |
+| `sent-integration-starter` | Stand up and harden a Sent v3 integration | [`skills/sent-integration-starter/SKILL.md`](skills/sent-integration-starter/SKILL.md) |
+| `sent-webhook-engineer` | Build and debug verified webhook receivers | [`skills/sent-webhook-engineer/SKILL.md`](skills/sent-webhook-engineer/SKILL.md) |
+| `sent-routing-strategist` | Choose channels and diagnose route outcomes | [`skills/sent-routing-strategist/SKILL.md`](skills/sent-routing-strategist/SKILL.md) |
+| `sent-two-way-messaging` | Design inbound, consent, and conversational flows | [`skills/sent-two-way-messaging/SKILL.md`](skills/sent-two-way-messaging/SKILL.md) |
+| `sent-profile-provisioning` | Execute the Sender Profile and user lifecycle | [`skills/sent-profile-provisioning/SKILL.md`](skills/sent-profile-provisioning/SKILL.md) |
+| `migrate-to-sent` | Migrate from another CPaaS provider onto Sent | [`skills/migrate-to-sent/SKILL.md`](skills/migrate-to-sent/SKILL.md) |
 
 To install the skills without the host adapter, list or select them with the Skills CLI:
 

diff --git a/adapter-sources/shared/marketplace.json b/adapter-sources/shared/marketplace.json
@@ -1,17 +1,17 @@
 {
   "display_name": "Sent",
   "short_description": "Business messaging workflows",
-  "long_description": "Use Sent MCP operations for safe account, contact, template, analytics, and messaging workflows. Focused specialist skills add delivery diagnosis, Sender Profile architecture, US A2P 10DLC registration, WhatsApp Business onboarding and template authoring, RCS agent launch readiness, and cross-channel template-builder design.",
+  "long_description": "Use Sent MCP operations for safe account, contact, template, analytics, and messaging workflows. Focused specialist skills add API integration, webhook engineering, contact-aware routing, two-way messaging, Sender Profile architecture and provisioning, CPaaS migration, delivery diagnosis, US A2P 10DLC, WhatsApp Business, RCS launch readiness, and cross-channel template design.",
   "developer_name": "Sent",
   "category": "Productivity",
   "capabilities": ["Interactive", "Write"],
   "website_url": "https://github.com/sentdm/sent-plugin#readme",
   "privacy_policy_url": "https://www.sent.dm/en/legal/privacy-policy",
   "terms_of_service_url": "https://www.sent.dm/en/legal/terms-of-service",
   "default_prompts": [
-    "Use $sent-account-readiness to check whether my Sent account is messaging-ready.",
-    "Use $messaging-performance-analyzer to diagnose this delivery report by channel.",
-    "Use $sms-10dlc-registration to review my US A2P registration evidence."
+    "Use $sent-integration-starter to review how this application should integrate Sent safely.",
+    "Use $sent-routing-strategist to explain the safest channel and reroute policy for this workflow.",
+    "Use $migrate-to-sent to plan a staged migration from our current messaging provider."
   ],
-  "marketplace_description": "Official Sent skills and remote MCP integration for messaging operations and specialist channel workflows."
+  "marketplace_description": "Official Sent skills and remote MCP integration for messaging engineering, operations, migration, and specialist channel workflows."
 }
diff --git a/claude-plugins/sent/.claude-plugin/plugin.json b/claude-plugins/sent/.claude-plugin/plugin.json
@@ -1,7 +1,7 @@
 {
   "name": "sent",
   "version": "0.1.0",
-  "description": "Official Sent business messaging plugin for safe SMS, WhatsApp, RCS, contacts, templates, analytics, account readiness, delivery diagnosis, 10DLC, WABA, RBM, and Sender Profile workflows.",
+  "description": "Official Sent business messaging plugin for SMS, WhatsApp, RCS, API integration, webhooks, routing, two-way messaging, Sender Profiles, migration, compliance, analytics, and agent-safe operations.",
   "author": {
     "name": "Sent",
     "url": "https://sent.dm"
@@ -27,6 +27,11 @@
     "analytics",
     "deliverability",
     "sender-profiles",
+    "api-integration",
+    "webhooks",
+    "routing",
+    "two-way-messaging",
+    "migration",
     "mcp"
   ],
   "commands": "./.claude/commands",

diff --git a/claude-plugins/sent/README.md b/claude-plugins/sent/README.md
@@ -19,6 +19,12 @@ This generated host adapter packages the official Sent Agent Skills and remote M
 | `rcs-agent-onboarding` | Prepare an RBM agent for approval and launch | [`skills/rcs-agent-onboarding/SKILL.md`](skills/rcs-agent-onboarding/SKILL.md) |
 | `sender-profile-architect` | Design multi-tenant Sender Profile architecture | [`skills/sender-profile-architect/SKILL.md`](skills/sender-profile-architect/SKILL.md) |
 | `template-builder-ui` | Design cross-channel template-builder UX | [`skills/template-builder-ui/SKILL.md`](skills/template-builder-ui/SKILL.md) |
+| `sent-integration-starter` | Stand up and harden a Sent v3 integration | [`skills/sent-integration-starter/SKILL.md`](skills/sent-integration-starter/SKILL.md) |
+| `sent-webhook-engineer` | Build and debug verified webhook receivers | [`skills/sent-webhook-engineer/SKILL.md`](skills/sent-webhook-engineer/SKILL.md) |
+| `sent-routing-strategist` | Choose channels and diagnose route outcomes | [`skills/sent-routing-strategist/SKILL.md`](skills/sent-routing-strategist/SKILL.md) |
+| `sent-two-way-messaging` | Design inbound, consent, and conversational flows | [`skills/sent-two-way-messaging/SKILL.md`](skills/sent-two-way-messaging/SKILL.md) |
+| `sent-profile-provisioning` | Execute the Sender Profile and user lifecycle | [`skills/sent-profile-provisioning/SKILL.md`](skills/sent-profile-provisioning/SKILL.md) |
+| `migrate-to-sent` | Migrate from another CPaaS provider onto Sent | [`skills/migrate-to-sent/SKILL.md`](skills/migrate-to-sent/SKILL.md) |
 
 To install the skills without the host adapter, list or select them with the Skills CLI:
 

diff --git a/claude-plugins/sent/skills/migrate-to-sent/SKILL.md b/claude-plugins/sent/skills/migrate-to-sent/SKILL.md
@@ -0,0 +1,95 @@
+---
+name: migrate-to-sent
+description: Plans and executes a migration from Twilio, Sinch, Infobip, Vonage, or MessageBird/Bird to Sent v3 — mapping send calls, status vocabularies, webhook signature schemes, opt-out stores, templates, and tenancy models, then cutting over safely with dual-run and rollback. Use when replacing an incumbent CPaaS provider, translating provider code or webhook handlers to Sent, or planning a phased cutover and its verification gates.
+---
+
+# Migrate to Sent
+
+Every migration from a major CPaaS provider hits the same five translation problems. Work them in this order, because the first one silently doubles cost and is invisible in tests.
+
+## 1. Ordered fallback becomes automatic routing
+
+Incumbent platforms express cross-channel delivery through different caller-side arrays, failover objects, messaging-service features, or application-level priority configuration. Do not assume those shapes have a direct Sent request-field equivalent.
+
+**Sent's `channel` array is a broadcast list.** Porting an ordered array produces one message and one charge per recipient-channel pair, which passes tests and multiplies production spend. The correct translation is automatic routing — omit `channel` or send `["sent"]` — which lets the platform select a route and reroute across up to three channel-and-provider pairs on the same `message_id`. Details belong to `sent-routing-strategist`; the migration rule is simply: **never port an ordered channel list.**
+
+## 2. Status vocabularies do not line up
+
+Incumbent statuses map onto Sent's, but Sent adds two states that have no equivalent and that break naive retry logic.
+
+| Sent status | Closest incumbent analogue | Migration note |
+| --- | --- | --- |
+| `QUEUED` | Twilio `queued`, Sinch `QUEUED_ON_CHANNEL` | Accepted, not sent |
+| `ROUTED` | no analogue | Route chosen; fires again on reroute |
+| `SENT` | Twilio `sent`, Sinch `MESSAGE_SUBMIT` | Provider handoff only |
+| `DELIVERED` | `delivered` everywhere | The first proof of handset receipt |
+| `READ` | Twilio `read`, Sinch `READ` | WhatsApp and RCS only |
+| `FAILED` | `failed`, `undelivered` | May still reroute; not necessarily final |
+| `FILTERED` | Twilio error 21610 (opt-out) | **Policy gate. Never retry** |
+| `BLOCKED` | account-level errors | **Account precondition.** Fix the account, then resend |
+| `SCHEDULED` | no analogue | Quiet-hours parking; resumes automatically |
+
+Two consequences for ported code. Handlers that treat every non-delivered terminal state as retryable will retry consent blocks, which is a compliance failure rather than a bug. And handlers keyed on numeric provider error codes — Twilio's `21610` is the classic — must be rewritten against Sent's string `error.code` families.
+
+## 3. Webhook verification is a rewrite, not a port
+
+No two providers sign the same way, and no Sent SDK ships a verifier.
+
+| Provider | Scheme |
+| --- | --- |
+| Twilio | `X-Twilio-Signature`, base64 HMAC-**SHA1** over the full URL plus sorted POST parameters |
+| Sinch | HMAC-SHA256 over `body.nonce.timestamp`, four `x-sinch-webhook-signature*` headers, or OAuth 2.0 |
+| Infobip | Basic, HMAC-SHA256 over the raw body, or OAuth on a notification profile; **the header name is account-configured** |
+| Vonage | JWT in `Authorization: Bearer`, or a legacy `sig` parameter |
+| MessageBird/Bird | `messagebird-signature`, base64 HMAC-SHA256 over timestamp, URL, and a SHA-256 body hash |
+| **Sent** | `x-webhook-signature: v1,{base64}`, HMAC-SHA256 over `{x-webhook-id}.{x-webhook-timestamp}.{raw_body}` |
+
+Sent's key is the signing secret with `whsec_` stripped and the remainder base64-decoded, compared in constant time, with timestamps outside 300 seconds rejected. Because Sent provides no per-event id, dedupe keys must be derived from payload semantics. Build the receiver with `sent-webhook-engineer` rather than adapting the incumbent's verifier.
+
+## 4. Opt-out stores must be reconciled, not migrated by copy
+
+Every provider keeps its own suppression list — Twilio Advanced Opt-Out, Infobip Blocklist, Sinch OPT_IN/OPT_OUT events. Sent enforces consent at the platform level before events reach the application, stores it as `opt_out` on the contact, and applies it **channel-agnostically**: a `STOP` on SMS suppresses WhatsApp and RCS too.
+
+Reconciliation rules: export the incumbent's suppression list before cutover, treat any opt-out on any incumbent channel as a global Sent opt-out, and never clear `opt_out` to "clean up" migrated data. Sent's ten default keywords are `STOP`, `CANCEL`, `UNSUBSCRIBE`, `QUIT`, `END`, `START`, `UNSTOP`, `SUBSCRIBE`, `HELP`, `INFO`, matched only when the entire trimmed body equals the keyword — so incumbent-specific keywords need custom keyword entries. Rewrite any incumbent keyword matcher as an exact local consent mirror and audit mechanism; the matcher must not write consent to Sent again. Consent semantics belong to `sent-two-way-messaging`.
+
+## 5. Templates and tenancy are re-registered, not transferred
+
+WhatsApp templates live with the WABA, so the migration question is whether the WABA moves. Positional placeholders (`{{1}}`, `{{2}}`) become **named** parameters in Sent, which means every call site that passed an ordered array must pass a named map. Approval is asynchronous and arrives as a `templates` webhook event, so build the template inventory before cutover rather than during it.
+
+Tenancy maps as follows, with the boundary decision owned by `sender-profile-architect` and the API work by `sent-profile-provisioning`:
+
+| Incumbent construct | Sent equivalent |
+| --- | --- |
+| Twilio subaccount | Sender Profile |
+| Twilio Messaging Service | routing plus profile configuration, not a caller-side pool |
+| Infobip Application or Entity | Sender Profile |
+| Sinch Conversation API app | Sender Profile |
+| Provider API credential per tenant | Profile-scoped API key, or organization key with `x-profile-id` |
+
+## Migration sequence
+
+1. **Inventory** every send call site, webhook handler, status branch, template, suppression list, and credential. Use `scripts/inventory_scan.py` to find them mechanically.
+2. **Map** each item using [references/provider-mapping.md](references/provider-mapping.md), flagging ordered-fallback arrays and numeric error codes as required rewrites.
+3. **Stand up Sent in parallel**: credentials, one webhook per environment, verified receiver, templates re-registered and approved.
+4. **Prove equivalence in sandbox** with `"sandbox": true`, then with a small live cohort confirmed to `DELIVERED`.
+5. **Dual-run** with a traffic split, comparing delivery rates, latency, and cost per message on the same message classes.
+6. **Cut over** by message class — lowest-risk transactional first, marketing last — keeping the incumbent receiver live.
+7. **Decommission** only after a full billing cycle of clean data, then revoke incumbent credentials.
+
+Sequencing detail, verification gates, and rollback triggers are in [references/cutover-playbook.md](references/cutover-playbook.md).
+
+## Mistakes that survive testing
+
+- Porting an ordered channel array. Doubles cost, never errors.
+- Treating `FILTERED` as retryable. Compliance exposure.
+- Reusing the incumbent's signature verifier. Every delivery returns 401.
+- Assuming `202` means delivered. Sent acknowledges acceptance only.
+- Keeping positional template placeholders. Parameters silently mismatch.
+- Retrying on `401`. Ten consecutive auth failures lock the credential with escalating lockout.
+- Omitting `Idempotency-Key` during dual-run. A timeout retry sends twice.
+- Sending `x-profile-id` with a profile-scoped key. Returns `403`.
+- Copying an incumbent's `Authorization: Bearer` pattern. Sent authenticates with `x-api-key`.
+
+## Boundaries
+
+This skill owns provider mapping and line-by-line migration planning. Hand the resulting Sent client and resilience work to `sent-integration-starter`, channel semantics to `sent-routing-strategist`, receiver construction to `sent-webhook-engineer`, WhatsApp onboarding to `waba-embedded-signup`, and US campaign registration to `sms-10dlc-registration`.
diff --git a/claude-plugins/sent/skills/migrate-to-sent/agents/openai.yaml b/claude-plugins/sent/skills/migrate-to-sent/agents/openai.yaml
@@ -0,0 +1,4 @@
+interface:
+  display_name: "Migrate to Sent"
+  short_description: "Move from another CPaaS provider to Sent"
+  default_prompt: "Use $migrate-to-sent to plan our move from our current messaging provider to Sent."