Update to Twilio Developer Kit

{
  "name": "twilio-messaging-overview",
  "description": "Twilio Messaging channel overview and onboarding guide. Covers all channels (SMS, WhatsApp, RCS, Facebook Messenger), the unified Messages API, channel selection guidance, and the recommended setup sequence from first message to production monitoring. Start here before choosing a specific messaging channel.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 231
    }
  ],
  "skill_md_contents": "---\nname: twilio-messaging-overview\ndescription: >\n  Twilio Messaging channel overview and onboarding guide. Covers all\n  channels (SMS, WhatsApp, RCS, Facebook Messenger), the unified\n  Messages API, channel selection guidance, and the recommended setup\n  sequence from first message to production monitoring. Start here\n  before choosing a specific messaging channel.\n---\n\n## Overview\n\nTwilio's Messaging platform sends and receives messages across multiple channels through a single API. All channels use `client.messages.create()` — only the address format changes.\n\n| Channel | Address format | Rich media | Template required? | Reach | Skill |\n|---------|---------------|------------|-------------------|-------|-------|\n| **SMS/MMS** | `+15551234567` (E.164) | MMS: images/video, US/CA/AU only | No | Global (180+ countries) | `twilio-sms-send-message` |\n| **WhatsApp** | `whatsapp:+15551234567` | Yes (images, docs, video, location) | Outside 24hr window: yes | 190+ countries | `twilio-whatsapp-send-message` |\n| **RCS** | Same number (via Messaging Service) | Yes (rich cards, carousels, video) | No | US + expanding globally | `twilio-rcs-messaging` |\n| **Facebook Messenger** | `messenger:{page-scoped-id}` | Yes | No | Global | — |\n\n---\n\n## Which Channel Should I Use?\n\n| If you need to... | Use | Why |\n|-------------------|-----|-----|\n| Reach any phone number | SMS | Universal — works on every phone, no app needed |\n| Send rich media globally | WhatsApp | Images, docs, video work worldwide (MMS is US/CA/AU only) |\n| Send time-sensitive alerts (OTP, outages) | SMS | Highest open rates, no app dependency |\n| Reach opted-in audience at lower cost | WhatsApp | No per-message fee in many markets |\n| Run marketing campaigns across channels | Start with `twilio-marketing-promotions-advisor` | Planner skill handles channel mix, compliance, and fallback |\n| Send transactional notifications | Start with `twilio-notifications-alerts-advisor` | Planner skill handles urgency-based channel routing |\n\n**Not sure?** Use a Planner skill first — it will qualify your use case and recommend the right channel combination.\n\n---\n\n## Unified API\n\nAll channels share `messages.create()`. The only difference is the address format in `from` and `to`.\n\n**Python**\n```python\nimport os\nfrom twilio.rest import Client\n\nclient = Client(os.environ[\"TWILIO_ACCOUNT_SID\"], os.environ[\"TWILIO_AUTH_TOKEN\"])\n\n# SMS\nsms = client.messages.create(\n    from_=\"+15017122661\",\n    to=\"+15558675310\",\n    body=\"Your order shipped.\"\n)\n\n# WhatsApp — same API, prefixed addresses\nwhatsapp = client.messages.create(\n    from_=\"whatsapp:+15017122661\",\n    to=\"whatsapp:+15558675310\",\n    body=\"Your order shipped.\"\n)\n```\n\n**Node.js**\n```javascript\nconst client = require(\"twilio\")(process.env.TWILIO_ACCOUNT_SID, process.env.TWILIO_AUTH_TOKEN);\n\n// SMS\nconst sms = await client.messages.create({\n    from: \"+15017122661\",\n    to: \"+15558675310\",\n    body: \"Your order shipped.\",\n});\n\n// WhatsApp — same API, prefixed addresses\nconst whatsapp = await client.messages.create({\n    from: \"whatsapp:+15017122661\",\n    to: \"whatsapp:+15558675310\",\n    body: \"Your order shipped.\",\n});\n```\n\n---\n\n## Onboarding Sequence\n\nSet up messaging in this order. Each step builds on the previous.\n\n### Step 1: Foundation\nGet a Twilio number, send your first SMS.\n- `twilio-account-setup` → `twilio-sms-send-message`\n\n### Step 2: Sender Strategy\nCreate a Messaging Service and add your numbers to a sender pool. Use `messagingServiceSid` instead of `from` for all production sends — this enables geo-match, sticky sender, and unlocks compliance features.\n- `twilio-messaging-services`\n\n### Step 3: Compliance\nRegister for A2P 10DLC (required for US SMS traffic). Set up opt-out handling.\n- `twilio-compliance-onboarding` → `twilio-compliance-traffic`\n\n### Step 4: Protect\nEnable SMS pumping protection (prevents artificial traffic inflation) and compliance toolkit (quiet hours, reassigned number detection) on your Messaging Service.\n- `twilio-messaging-services` (Compliance Toolkit + SMS Pumping Protection sections)\n\n### Step 5: Add Channels\nAdd WhatsApp or other channels. Use Content Templates for cross-channel message formatting.\n- `twilio-whatsapp-send-message` → `twilio-content-template-builder`\n\n### Step 6: Monitor\nEnable intelligent alerts for error pattern detection. Set up status callbacks for delivery tracking.\n- `twilio-messaging-services` (Intelligent Alerts section) → `twilio-messaging-webhooks`\n\n---\n\n## CANNOT\n\n- **Cannot send cross-channel in a single API call** — Each `messages.create()` targets one channel. For multi-channel fallback, implement sequencing in your application (e.g., try SMS, on failure send WhatsApp).\n- **Cannot use WhatsApp free-form messages outside the 24-hour window** — After 24 hours since the user's last inbound message, you must use a pre-approved template. See `twilio-whatsapp-send-message`.\n- **Cannot send MMS outside US, Canada, and Australia** — MMS is only supported on US/CA/AU numbers. For international rich media, use WhatsApp.\n- **Cannot use SMS pumping protection or compliance toolkit without a Messaging Service** — These features are configured per Messaging Service. Raw `from` number sends don't get these protections.\n- **Cannot mix channels in a single Messaging Service sender pool** — A Messaging Service manages phone numbers for SMS/MMS. WhatsApp senders are configured separately.\n- **Cannot guarantee delivery on any channel** — SMS can be carrier-filtered, WhatsApp can queue-timeout (4 hours). Always implement status callbacks to track delivery.\n\n---\n\n## Next Steps\n\n- **Send SMS:** `twilio-sms-send-message`\n- **Send RCS:** `twilio-rcs-messaging`\n- **Send WhatsApp:** `twilio-whatsapp-send-message`\n- **Set up sender pools and production features:** `twilio-messaging-services`\n- **Channel selection for marketing:** `twilio-marketing-promotions-advisor`\n- **Channel selection for notifications:** `twilio-notifications-alerts-advisor`\n"
}