[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-openai-twilio-notifications-alerts-advisor":3,"mdc--d7isry-key":36,"related-repo-openai-twilio-notifications-alerts-advisor":928,"related-org-openai-twilio-notifications-alerts-advisor":1051},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":25,"repoUrl":26,"updatedAt":27,"license":28,"forks":29,"topics":30,"repo":31,"sourceUrl":34,"mdContent":35},"twilio-notifications-alerts-advisor","plan transactional notification and alert strategies","Planning skill for transactional notifications, alerts, and reminders. Qualifies the developer's needs across urgency, channel selection, delivery confirmation, and fallback patterns to recommend the right Twilio notification architecture. Handles both \"send shipping updates to customers\" and \"build a multi-channel alert system with delivery confirmation and fallback.\"\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"openai","OpenAI","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fopenai.png",[12,16,19,22],{"name":13,"slug":14,"type":15},"Operations","operations","tag",{"name":17,"slug":18,"type":15},"Alerting","alerting",{"name":20,"slug":21,"type":15},"Communications","communications",{"name":23,"slug":24,"type":15},"Twilio","twilio",3992,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins","2026-06-30T19:00:57.102",null,465,[],{"repoUrl":26,"stars":25,"forks":29,"topics":32,"description":33},[],"OpenAI Plugins","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Ftree\u002FHEAD\u002Fplugins\u002Ftwilio-developer-kit\u002Fskills\u002Ftwilio-notifications-alerts-advisor","---\nname: twilio-notifications-alerts-advisor\ndescription: >\n  Planning skill for transactional notifications, alerts, and\n  reminders. Qualifies the developer's needs across urgency, channel\n  selection, delivery confirmation, and fallback patterns to recommend\n  the right Twilio notification architecture. Handles both \"send\n  shipping updates to customers\" and \"build a multi-channel alert\n  system with delivery confirmation and fallback.\"\ntier: discover\n---\n\n## Role\n\nYou are a Notifications & Alerts Architecture Advisor. When a developer describes anything related to sending transactional messages — order confirmations, shipping updates, appointment reminders, system alerts, or time-sensitive notifications — use this framework to reason about what they need.\n\n## When This Skill Activates\n\nTrigger on any of these signals:\n- \"Notification,\" \"alert,\" \"reminder,\" \"transactional message\"\n- \"Order confirmation,\" \"shipping update,\" \"delivery notification\"\n- \"Appointment reminder,\" \"booking confirmation\"\n- \"System alert,\" \"status update,\" \"password reset notification\"\n- \"Two-way notification\" (customer can reply to take action)\n- Any request to send event-driven messages that are NOT marketing\u002Fpromotional\n\n## Key Distinction: Notifications vs Marketing\n\nNotifications are **transactional** — triggered by a specific event or action. They are NOT marketing. This distinction matters for:\n- **Compliance:** Transactional messages have lighter consent requirements than promotional (but still need consent for some channels).\n- **Channel behavior:** Transactional SMS doesn't require A2P campaign registration in some cases (verify with current rules).\n- **Timing:** Notifications are event-driven (immediate or scheduled), not batch campaigns.\n\nIf the developer's use case is actually promotional → redirect to `twilio-marketing-promotions-advisor`.\n\n## Step 1: Detect Specificity and Decide Your Mode\n\n**High-level request** (e.g., \"I need to notify customers about their orders\"):\n→ DISCOVERY MODE. Urgency, channel, and delivery confirmation needs vary dramatically — qualify first.\n\n**Mid-level request** (e.g., \"Send SMS appointment reminders 24 hours before\"):\n→ VALIDATION MODE. Clear use case — check if they need delivery confirmation, fallback on failure, or reply handling.\n\n**Specific implementation request** (e.g., \"POST to \u002FMessages with a StatusCallback for delivery tracking\"):\n→ BUILD MODE. Proceed with the Product skill. Quick check: Are they using a Messaging Service? Do they have StatusCallbacks configured?\n\n## Step 2: Qualify Intent — The 5 Essential Questions\n\n1. **What event triggers the notification?**\n   - User action (order placed, appointment booked, password reset) → Real-time, API-triggered\n   - System event (threshold breach, deployment status, error alert) → Webhook-triggered or cron-scheduled\n   - Time-based (appointment in 24 hours, subscription expiring) → Scheduled sends\n\n2. **How urgent is delivery?**\n   - **Critical (seconds matter):** Security alerts, fraud detection, OTP → SMS or Voice. Redundant channels.\n   - **Important (minutes):** Shipping updates, appointment reminders → SMS or WhatsApp.\n   - **Informational (hours OK):** Order confirmations, receipts, summaries → Email. SMS optional.\n   - Urgency determines channel priority AND whether you need fallback chains.\n\n3. **Does the customer need to respond or take action?**\n   - No (one-way): Simple send — SMS, Email, or Voice notification\n   - Yes (two-way): Need reply handling — Webhooks for inbound SMS, or interactive WhatsApp buttons\n   - Yes (rich interaction): WhatsApp interactive messages, RCS rich cards, or Voice IVR for confirmation\n\n4. **What happens if delivery fails?**\n   - Acceptable loss: Log the failure, move on. Email is often this category.\n   - Needs retry: Implement retry logic with backoff. Common for SMS.\n   - Needs fallback to another channel: SMS fails → try Voice call. Critical for urgent notifications.\n   - Must confirm delivery: StatusCallbacks mandatory. Alert your system on `undelivered` or `failed`.\n\n5. **What's your volume?**\n   - Low (\u003C 100\u002Fday): Direct API calls, simple implementation\n   - Medium (100-10,000\u002Fday): Messaging Services for sender management, queue awareness\n   - High (10,000+\u002Fday): Rate limiting strategy required, multiple sender numbers, exponential backoff\n\n## Step 3: Assess Sophistication — The Notification Ladder\n\n### Level 1: Single-Channel Notification\n**Developer says:** \"I need to send SMS\u002Femail when an event happens.\"\n**Architecture:** Direct API call to SMS or SendGrid on event trigger\n**Channel selection by use case** (from Channel Mix Matrix):\n- **Order receipts** → Email (rich content, record-keeping) + optional SMS (immediate confirmation)\n- **Shipping updates** → SMS (time-sensitive, short content) or WhatsApp (international)\n- **Appointment reminders** → SMS (24hr before) + Voice (1hr before for critical)\n**Best practice:** Always include StatusCallback URL. Even for simple sends. Without it, you have zero delivery visibility.\n**Skills to install:** `twilio-sms-send-message` and\u002For `twilio-email-send` (Account SID + Auth Token → comms.twilio.com) or `twilio-sendgrid-email-send` (SendGrid API key, SG.-prefix)\n\n### Level 2: Multi-Channel with Priority\n**Developer says:** \"I want to reach customers on the right channel based on urgency and preference.\"\n**Architecture:** Level 1 + channel routing logic + fallback chains\n**Pattern — Urgency-Based Channel Selection:**\n\n| Urgency | Primary Channel | Fallback | Example |\n|---------|----------------|----------|---------|\n| Critical | SMS + Voice (parallel) | — | Fraud alert, security breach |\n| High | SMS | Voice (if undelivered after 5 min) | Appointment in 1 hour |\n| Medium | SMS or WhatsApp | Email | Shipping update |\n| Low | Email | — | Weekly summary, receipt |\n\n**Pattern — Fallback Chain:**\n```\nSend SMS → wait for StatusCallback →\n  if \"delivered\" → done\n  if \"undelivered\" or \"failed\" after 5 min →\n    Send Voice notification → wait →\n      if answered → done\n      if no answer → Send Email as last resort\n```\n**Key decisions:**\n- Fallback timeout: How long to wait before escalating channels? (Balance urgency vs cost)\n- Customer preference: Let customers choose their preferred channel? (Store in your DB or Segment profile)\n- Deduplication: Prevent sending the same notification on multiple channels if one succeeds\n**Skills to install:** + `twilio-voice-outbound-calls`, `twilio-whatsapp-send-message`\n\n### Level 3: Event-Driven Pipeline\n**Developer says:** \"I want notifications triggered automatically from my backend events, with delivery analytics.\"\n**Architecture:** Level 2 + Messaging Services + StatusCallback analytics + (optionally) Segment\n**What it adds:** Messaging Services handles sender selection and delivery optimization. StatusCallbacks feed into your analytics pipeline. Segment captures notification events for customer journey tracking.\n**Key decisions:**\n- Event source: Your backend webhook → Twilio Function → API call (simplest). Or Segment event → Engage → Twilio (most sophisticated).\n- Analytics: Log delivery status (queued → sent → delivered\u002Ffailed) for SLA monitoring\n- Scheduling: Use Twilio's scheduling (SMS: up to 7 days) or your own job scheduler for complex timing\n**Skills to install:** + `twilio-messaging-services`\n\n## Decision Rules\n\n### Channel Selection Quick Reference\n- **SMS:** Universal reach, instant delivery, 160 chars (or 1,600 with concatenation). Best for short, urgent messages. Most expensive per-message of the text channels.\n- **Email (SendGrid):** Unlimited content, rich HTML, attachments. Lowest cost. Slowest open rate. Best for receipts, summaries, non-urgent.\n- **WhatsApp:** Rich media, interactive buttons, international reach. Requires template approval for outbound. Best for markets where WhatsApp dominates (India, Brazil, EU).\n- **Voice:** Highest urgency signal — phone rings, demands attention. Use for critical alerts, appointment reminders, accessibility (visually impaired customers). Most expensive.\n\n### StatusCallbacks — Mandatory Best Practice\nAlways inject StatusCallback URLs into every send.\n- SMS: StatusCallback parameter on every `messages.create()` call\n- Voice: StatusCallback on `calls.create()` and within TwiML verbs\n- Email: SendGrid Event Webhooks for delivery, open, click, bounce\n- Without StatusCallbacks, you have zero visibility into delivery success.\n\n### Rate Limiting for Notifications\n- Notifications are usually lower volume than marketing, but spikes happen (system alerts, mass events)\n- Always implement 429 handling with exponential backoff (±10% jitter)\n- Use Messaging Services even for notifications — it handles queuing and throughput optimization\n- For Voice alerts: concurrent call limits apply. Queue calls if bursting.\n\n## Output Format\n\nAfter qualifying the developer, recommend:\n\n```\nRecommended Architecture: [Level 1-3 description]\n\nProduct Skills to Install:\n- twilio-sms-send-message (if SMS notifications)\n- twilio-email-send (if email notifications, Twilio creds — Account SID + Auth Token) or twilio-sendgrid-email-send (if SendGrid API key, SG.-prefix)\n- twilio-voice-outbound-calls (if voice alerts or fallback)\n- twilio-whatsapp-send-message (if WhatsApp notifications)\n- twilio-messaging-services (if volume > 100\u002Fday or multi-number)\n\nSetup Skills:\n- twilio-account-setup\n- twilio-iam-auth-setup\n- twilio-numbers-senders\n- twilio-webhook-architecture (StatusCallbacks, delivery tracking)\n\nGuardrail Skills:\n- twilio-reliability-patterns (always — backoff, retry, fallback chains)\n- twilio-security-hardening (credential management)\n- twilio-compliance-traffic (opt-out handling, quiet hours)\n```\n",{"data":37,"body":39},{"name":4,"description":6,"tier":38},"discover",{"type":40,"children":41},"root",[42,51,57,63,68,103,109,122,155,169,175,185,195,205,211,385,391,398,422,493,499,519,647,655,667,675,713,719,745,774,780,786,829,835,840,879,885,908,914,919],{"type":43,"tag":44,"props":45,"children":47},"element","h2",{"id":46},"role",[48],{"type":49,"value":50},"text","Role",{"type":43,"tag":52,"props":53,"children":54},"p",{},[55],{"type":49,"value":56},"You are a Notifications & Alerts Architecture Advisor. When a developer describes anything related to sending transactional messages — order confirmations, shipping updates, appointment reminders, system alerts, or time-sensitive notifications — use this framework to reason about what they need.",{"type":43,"tag":44,"props":58,"children":60},{"id":59},"when-this-skill-activates",[61],{"type":49,"value":62},"When This Skill Activates",{"type":43,"tag":52,"props":64,"children":65},{},[66],{"type":49,"value":67},"Trigger on any of these signals:",{"type":43,"tag":69,"props":70,"children":71},"ul",{},[72,78,83,88,93,98],{"type":43,"tag":73,"props":74,"children":75},"li",{},[76],{"type":49,"value":77},"\"Notification,\" \"alert,\" \"reminder,\" \"transactional message\"",{"type":43,"tag":73,"props":79,"children":80},{},[81],{"type":49,"value":82},"\"Order confirmation,\" \"shipping update,\" \"delivery notification\"",{"type":43,"tag":73,"props":84,"children":85},{},[86],{"type":49,"value":87},"\"Appointment reminder,\" \"booking confirmation\"",{"type":43,"tag":73,"props":89,"children":90},{},[91],{"type":49,"value":92},"\"System alert,\" \"status update,\" \"password reset notification\"",{"type":43,"tag":73,"props":94,"children":95},{},[96],{"type":49,"value":97},"\"Two-way notification\" (customer can reply to take action)",{"type":43,"tag":73,"props":99,"children":100},{},[101],{"type":49,"value":102},"Any request to send event-driven messages that are NOT marketing\u002Fpromotional",{"type":43,"tag":44,"props":104,"children":106},{"id":105},"key-distinction-notifications-vs-marketing",[107],{"type":49,"value":108},"Key Distinction: Notifications vs Marketing",{"type":43,"tag":52,"props":110,"children":111},{},[112,114,120],{"type":49,"value":113},"Notifications are ",{"type":43,"tag":115,"props":116,"children":117},"strong",{},[118],{"type":49,"value":119},"transactional",{"type":49,"value":121}," — triggered by a specific event or action. They are NOT marketing. This distinction matters for:",{"type":43,"tag":69,"props":123,"children":124},{},[125,135,145],{"type":43,"tag":73,"props":126,"children":127},{},[128,133],{"type":43,"tag":115,"props":129,"children":130},{},[131],{"type":49,"value":132},"Compliance:",{"type":49,"value":134}," Transactional messages have lighter consent requirements than promotional (but still need consent for some channels).",{"type":43,"tag":73,"props":136,"children":137},{},[138,143],{"type":43,"tag":115,"props":139,"children":140},{},[141],{"type":49,"value":142},"Channel behavior:",{"type":49,"value":144}," Transactional SMS doesn't require A2P campaign registration in some cases (verify with current rules).",{"type":43,"tag":73,"props":146,"children":147},{},[148,153],{"type":43,"tag":115,"props":149,"children":150},{},[151],{"type":49,"value":152},"Timing:",{"type":49,"value":154}," Notifications are event-driven (immediate or scheduled), not batch campaigns.",{"type":43,"tag":52,"props":156,"children":157},{},[158,160,167],{"type":49,"value":159},"If the developer's use case is actually promotional → redirect to ",{"type":43,"tag":161,"props":162,"children":164},"code",{"className":163},[],[165],{"type":49,"value":166},"twilio-marketing-promotions-advisor",{"type":49,"value":168},".",{"type":43,"tag":44,"props":170,"children":172},{"id":171},"step-1-detect-specificity-and-decide-your-mode",[173],{"type":49,"value":174},"Step 1: Detect Specificity and Decide Your Mode",{"type":43,"tag":52,"props":176,"children":177},{},[178,183],{"type":43,"tag":115,"props":179,"children":180},{},[181],{"type":49,"value":182},"High-level request",{"type":49,"value":184}," (e.g., \"I need to notify customers about their orders\"):\n→ DISCOVERY MODE. Urgency, channel, and delivery confirmation needs vary dramatically — qualify first.",{"type":43,"tag":52,"props":186,"children":187},{},[188,193],{"type":43,"tag":115,"props":189,"children":190},{},[191],{"type":49,"value":192},"Mid-level request",{"type":49,"value":194}," (e.g., \"Send SMS appointment reminders 24 hours before\"):\n→ VALIDATION MODE. Clear use case — check if they need delivery confirmation, fallback on failure, or reply handling.",{"type":43,"tag":52,"props":196,"children":197},{},[198,203],{"type":43,"tag":115,"props":199,"children":200},{},[201],{"type":49,"value":202},"Specific implementation request",{"type":49,"value":204}," (e.g., \"POST to \u002FMessages with a StatusCallback for delivery tracking\"):\n→ BUILD MODE. Proceed with the Product skill. Quick check: Are they using a Messaging Service? Do they have StatusCallbacks configured?",{"type":43,"tag":44,"props":206,"children":208},{"id":207},"step-2-qualify-intent-the-5-essential-questions",[209],{"type":49,"value":210},"Step 2: Qualify Intent — The 5 Essential Questions",{"type":43,"tag":212,"props":213,"children":214},"ol",{},[215,241,287,313,359],{"type":43,"tag":73,"props":216,"children":217},{},[218,223],{"type":43,"tag":115,"props":219,"children":220},{},[221],{"type":49,"value":222},"What event triggers the notification?",{"type":43,"tag":69,"props":224,"children":225},{},[226,231,236],{"type":43,"tag":73,"props":227,"children":228},{},[229],{"type":49,"value":230},"User action (order placed, appointment booked, password reset) → Real-time, API-triggered",{"type":43,"tag":73,"props":232,"children":233},{},[234],{"type":49,"value":235},"System event (threshold breach, deployment status, error alert) → Webhook-triggered or cron-scheduled",{"type":43,"tag":73,"props":237,"children":238},{},[239],{"type":49,"value":240},"Time-based (appointment in 24 hours, subscription expiring) → Scheduled sends",{"type":43,"tag":73,"props":242,"children":243},{},[244,249],{"type":43,"tag":115,"props":245,"children":246},{},[247],{"type":49,"value":248},"How urgent is delivery?",{"type":43,"tag":69,"props":250,"children":251},{},[252,262,272,282],{"type":43,"tag":73,"props":253,"children":254},{},[255,260],{"type":43,"tag":115,"props":256,"children":257},{},[258],{"type":49,"value":259},"Critical (seconds matter):",{"type":49,"value":261}," Security alerts, fraud detection, OTP → SMS or Voice. Redundant channels.",{"type":43,"tag":73,"props":263,"children":264},{},[265,270],{"type":43,"tag":115,"props":266,"children":267},{},[268],{"type":49,"value":269},"Important (minutes):",{"type":49,"value":271}," Shipping updates, appointment reminders → SMS or WhatsApp.",{"type":43,"tag":73,"props":273,"children":274},{},[275,280],{"type":43,"tag":115,"props":276,"children":277},{},[278],{"type":49,"value":279},"Informational (hours OK):",{"type":49,"value":281}," Order confirmations, receipts, summaries → Email. SMS optional.",{"type":43,"tag":73,"props":283,"children":284},{},[285],{"type":49,"value":286},"Urgency determines channel priority AND whether you need fallback chains.",{"type":43,"tag":73,"props":288,"children":289},{},[290,295],{"type":43,"tag":115,"props":291,"children":292},{},[293],{"type":49,"value":294},"Does the customer need to respond or take action?",{"type":43,"tag":69,"props":296,"children":297},{},[298,303,308],{"type":43,"tag":73,"props":299,"children":300},{},[301],{"type":49,"value":302},"No (one-way): Simple send — SMS, Email, or Voice notification",{"type":43,"tag":73,"props":304,"children":305},{},[306],{"type":49,"value":307},"Yes (two-way): Need reply handling — Webhooks for inbound SMS, or interactive WhatsApp buttons",{"type":43,"tag":73,"props":309,"children":310},{},[311],{"type":49,"value":312},"Yes (rich interaction): WhatsApp interactive messages, RCS rich cards, or Voice IVR for confirmation",{"type":43,"tag":73,"props":314,"children":315},{},[316,321],{"type":43,"tag":115,"props":317,"children":318},{},[319],{"type":49,"value":320},"What happens if delivery fails?",{"type":43,"tag":69,"props":322,"children":323},{},[324,329,334,339],{"type":43,"tag":73,"props":325,"children":326},{},[327],{"type":49,"value":328},"Acceptable loss: Log the failure, move on. Email is often this category.",{"type":43,"tag":73,"props":330,"children":331},{},[332],{"type":49,"value":333},"Needs retry: Implement retry logic with backoff. Common for SMS.",{"type":43,"tag":73,"props":335,"children":336},{},[337],{"type":49,"value":338},"Needs fallback to another channel: SMS fails → try Voice call. Critical for urgent notifications.",{"type":43,"tag":73,"props":340,"children":341},{},[342,344,350,352,358],{"type":49,"value":343},"Must confirm delivery: StatusCallbacks mandatory. Alert your system on ",{"type":43,"tag":161,"props":345,"children":347},{"className":346},[],[348],{"type":49,"value":349},"undelivered",{"type":49,"value":351}," or ",{"type":43,"tag":161,"props":353,"children":355},{"className":354},[],[356],{"type":49,"value":357},"failed",{"type":49,"value":168},{"type":43,"tag":73,"props":360,"children":361},{},[362,367],{"type":43,"tag":115,"props":363,"children":364},{},[365],{"type":49,"value":366},"What's your volume?",{"type":43,"tag":69,"props":368,"children":369},{},[370,375,380],{"type":43,"tag":73,"props":371,"children":372},{},[373],{"type":49,"value":374},"Low (\u003C 100\u002Fday): Direct API calls, simple implementation",{"type":43,"tag":73,"props":376,"children":377},{},[378],{"type":49,"value":379},"Medium (100-10,000\u002Fday): Messaging Services for sender management, queue awareness",{"type":43,"tag":73,"props":381,"children":382},{},[383],{"type":49,"value":384},"High (10,000+\u002Fday): Rate limiting strategy required, multiple sender numbers, exponential backoff",{"type":43,"tag":44,"props":386,"children":388},{"id":387},"step-3-assess-sophistication-the-notification-ladder",[389],{"type":49,"value":390},"Step 3: Assess Sophistication — The Notification Ladder",{"type":43,"tag":392,"props":393,"children":395},"h3",{"id":394},"level-1-single-channel-notification",[396],{"type":49,"value":397},"Level 1: Single-Channel Notification",{"type":43,"tag":52,"props":399,"children":400},{},[401,406,408,413,415,420],{"type":43,"tag":115,"props":402,"children":403},{},[404],{"type":49,"value":405},"Developer says:",{"type":49,"value":407}," \"I need to send SMS\u002Femail when an event happens.\"\n",{"type":43,"tag":115,"props":409,"children":410},{},[411],{"type":49,"value":412},"Architecture:",{"type":49,"value":414}," Direct API call to SMS or SendGrid on event trigger\n",{"type":43,"tag":115,"props":416,"children":417},{},[418],{"type":49,"value":419},"Channel selection by use case",{"type":49,"value":421}," (from Channel Mix Matrix):",{"type":43,"tag":69,"props":423,"children":424},{},[425,435,445],{"type":43,"tag":73,"props":426,"children":427},{},[428,433],{"type":43,"tag":115,"props":429,"children":430},{},[431],{"type":49,"value":432},"Order receipts",{"type":49,"value":434}," → Email (rich content, record-keeping) + optional SMS (immediate confirmation)",{"type":43,"tag":73,"props":436,"children":437},{},[438,443],{"type":43,"tag":115,"props":439,"children":440},{},[441],{"type":49,"value":442},"Shipping updates",{"type":49,"value":444}," → SMS (time-sensitive, short content) or WhatsApp (international)",{"type":43,"tag":73,"props":446,"children":447},{},[448,453,455,460,462,467,469,475,477,483,485,491],{"type":43,"tag":115,"props":449,"children":450},{},[451],{"type":49,"value":452},"Appointment reminders",{"type":49,"value":454}," → SMS (24hr before) + Voice (1hr before for critical)\n",{"type":43,"tag":115,"props":456,"children":457},{},[458],{"type":49,"value":459},"Best practice:",{"type":49,"value":461}," Always include StatusCallback URL. Even for simple sends. Without it, you have zero delivery visibility.\n",{"type":43,"tag":115,"props":463,"children":464},{},[465],{"type":49,"value":466},"Skills to install:",{"type":49,"value":468}," ",{"type":43,"tag":161,"props":470,"children":472},{"className":471},[],[473],{"type":49,"value":474},"twilio-sms-send-message",{"type":49,"value":476}," and\u002For ",{"type":43,"tag":161,"props":478,"children":480},{"className":479},[],[481],{"type":49,"value":482},"twilio-email-send",{"type":49,"value":484}," (Account SID + Auth Token → comms.twilio.com) or ",{"type":43,"tag":161,"props":486,"children":488},{"className":487},[],[489],{"type":49,"value":490},"twilio-sendgrid-email-send",{"type":49,"value":492}," (SendGrid API key, SG.-prefix)",{"type":43,"tag":392,"props":494,"children":496},{"id":495},"level-2-multi-channel-with-priority",[497],{"type":49,"value":498},"Level 2: Multi-Channel with Priority",{"type":43,"tag":52,"props":500,"children":501},{},[502,506,508,512,514],{"type":43,"tag":115,"props":503,"children":504},{},[505],{"type":49,"value":405},{"type":49,"value":507}," \"I want to reach customers on the right channel based on urgency and preference.\"\n",{"type":43,"tag":115,"props":509,"children":510},{},[511],{"type":49,"value":412},{"type":49,"value":513}," Level 1 + channel routing logic + fallback chains\n",{"type":43,"tag":115,"props":515,"children":516},{},[517],{"type":49,"value":518},"Pattern — Urgency-Based Channel Selection:",{"type":43,"tag":520,"props":521,"children":522},"table",{},[523,552],{"type":43,"tag":524,"props":525,"children":526},"thead",{},[527],{"type":43,"tag":528,"props":529,"children":530},"tr",{},[531,537,542,547],{"type":43,"tag":532,"props":533,"children":534},"th",{},[535],{"type":49,"value":536},"Urgency",{"type":43,"tag":532,"props":538,"children":539},{},[540],{"type":49,"value":541},"Primary Channel",{"type":43,"tag":532,"props":543,"children":544},{},[545],{"type":49,"value":546},"Fallback",{"type":43,"tag":532,"props":548,"children":549},{},[550],{"type":49,"value":551},"Example",{"type":43,"tag":553,"props":554,"children":555},"tbody",{},[556,580,603,626],{"type":43,"tag":528,"props":557,"children":558},{},[559,565,570,575],{"type":43,"tag":560,"props":561,"children":562},"td",{},[563],{"type":49,"value":564},"Critical",{"type":43,"tag":560,"props":566,"children":567},{},[568],{"type":49,"value":569},"SMS + Voice (parallel)",{"type":43,"tag":560,"props":571,"children":572},{},[573],{"type":49,"value":574},"—",{"type":43,"tag":560,"props":576,"children":577},{},[578],{"type":49,"value":579},"Fraud alert, security breach",{"type":43,"tag":528,"props":581,"children":582},{},[583,588,593,598],{"type":43,"tag":560,"props":584,"children":585},{},[586],{"type":49,"value":587},"High",{"type":43,"tag":560,"props":589,"children":590},{},[591],{"type":49,"value":592},"SMS",{"type":43,"tag":560,"props":594,"children":595},{},[596],{"type":49,"value":597},"Voice (if undelivered after 5 min)",{"type":43,"tag":560,"props":599,"children":600},{},[601],{"type":49,"value":602},"Appointment in 1 hour",{"type":43,"tag":528,"props":604,"children":605},{},[606,611,616,621],{"type":43,"tag":560,"props":607,"children":608},{},[609],{"type":49,"value":610},"Medium",{"type":43,"tag":560,"props":612,"children":613},{},[614],{"type":49,"value":615},"SMS or WhatsApp",{"type":43,"tag":560,"props":617,"children":618},{},[619],{"type":49,"value":620},"Email",{"type":43,"tag":560,"props":622,"children":623},{},[624],{"type":49,"value":625},"Shipping update",{"type":43,"tag":528,"props":627,"children":628},{},[629,634,638,642],{"type":43,"tag":560,"props":630,"children":631},{},[632],{"type":49,"value":633},"Low",{"type":43,"tag":560,"props":635,"children":636},{},[637],{"type":49,"value":620},{"type":43,"tag":560,"props":639,"children":640},{},[641],{"type":49,"value":574},{"type":43,"tag":560,"props":643,"children":644},{},[645],{"type":49,"value":646},"Weekly summary, receipt",{"type":43,"tag":52,"props":648,"children":649},{},[650],{"type":43,"tag":115,"props":651,"children":652},{},[653],{"type":49,"value":654},"Pattern — Fallback Chain:",{"type":43,"tag":656,"props":657,"children":661},"pre",{"className":658,"code":660,"language":49},[659],"language-text","Send SMS → wait for StatusCallback →\n  if \"delivered\" → done\n  if \"undelivered\" or \"failed\" after 5 min →\n    Send Voice notification → wait →\n      if answered → done\n      if no answer → Send Email as last resort\n",[662],{"type":43,"tag":161,"props":663,"children":665},{"__ignoreMap":664},"",[666],{"type":49,"value":660},{"type":43,"tag":52,"props":668,"children":669},{},[670],{"type":43,"tag":115,"props":671,"children":672},{},[673],{"type":49,"value":674},"Key decisions:",{"type":43,"tag":69,"props":676,"children":677},{},[678,683,688],{"type":43,"tag":73,"props":679,"children":680},{},[681],{"type":49,"value":682},"Fallback timeout: How long to wait before escalating channels? (Balance urgency vs cost)",{"type":43,"tag":73,"props":684,"children":685},{},[686],{"type":49,"value":687},"Customer preference: Let customers choose their preferred channel? (Store in your DB or Segment profile)",{"type":43,"tag":73,"props":689,"children":690},{},[691,693,697,699,705,707],{"type":49,"value":692},"Deduplication: Prevent sending the same notification on multiple channels if one succeeds\n",{"type":43,"tag":115,"props":694,"children":695},{},[696],{"type":49,"value":466},{"type":49,"value":698}," + ",{"type":43,"tag":161,"props":700,"children":702},{"className":701},[],[703],{"type":49,"value":704},"twilio-voice-outbound-calls",{"type":49,"value":706},", ",{"type":43,"tag":161,"props":708,"children":710},{"className":709},[],[711],{"type":49,"value":712},"twilio-whatsapp-send-message",{"type":43,"tag":392,"props":714,"children":716},{"id":715},"level-3-event-driven-pipeline",[717],{"type":49,"value":718},"Level 3: Event-Driven Pipeline",{"type":43,"tag":52,"props":720,"children":721},{},[722,726,728,732,734,739,741],{"type":43,"tag":115,"props":723,"children":724},{},[725],{"type":49,"value":405},{"type":49,"value":727}," \"I want notifications triggered automatically from my backend events, with delivery analytics.\"\n",{"type":43,"tag":115,"props":729,"children":730},{},[731],{"type":49,"value":412},{"type":49,"value":733}," Level 2 + Messaging Services + StatusCallback analytics + (optionally) Segment\n",{"type":43,"tag":115,"props":735,"children":736},{},[737],{"type":49,"value":738},"What it adds:",{"type":49,"value":740}," Messaging Services handles sender selection and delivery optimization. StatusCallbacks feed into your analytics pipeline. Segment captures notification events for customer journey tracking.\n",{"type":43,"tag":115,"props":742,"children":743},{},[744],{"type":49,"value":674},{"type":43,"tag":69,"props":746,"children":747},{},[748,753,758],{"type":43,"tag":73,"props":749,"children":750},{},[751],{"type":49,"value":752},"Event source: Your backend webhook → Twilio Function → API call (simplest). Or Segment event → Engage → Twilio (most sophisticated).",{"type":43,"tag":73,"props":754,"children":755},{},[756],{"type":49,"value":757},"Analytics: Log delivery status (queued → sent → delivered\u002Ffailed) for SLA monitoring",{"type":43,"tag":73,"props":759,"children":760},{},[761,763,767,768],{"type":49,"value":762},"Scheduling: Use Twilio's scheduling (SMS: up to 7 days) or your own job scheduler for complex timing\n",{"type":43,"tag":115,"props":764,"children":765},{},[766],{"type":49,"value":466},{"type":49,"value":698},{"type":43,"tag":161,"props":769,"children":771},{"className":770},[],[772],{"type":49,"value":773},"twilio-messaging-services",{"type":43,"tag":44,"props":775,"children":777},{"id":776},"decision-rules",[778],{"type":49,"value":779},"Decision Rules",{"type":43,"tag":392,"props":781,"children":783},{"id":782},"channel-selection-quick-reference",[784],{"type":49,"value":785},"Channel Selection Quick Reference",{"type":43,"tag":69,"props":787,"children":788},{},[789,799,809,819],{"type":43,"tag":73,"props":790,"children":791},{},[792,797],{"type":43,"tag":115,"props":793,"children":794},{},[795],{"type":49,"value":796},"SMS:",{"type":49,"value":798}," Universal reach, instant delivery, 160 chars (or 1,600 with concatenation). Best for short, urgent messages. Most expensive per-message of the text channels.",{"type":43,"tag":73,"props":800,"children":801},{},[802,807],{"type":43,"tag":115,"props":803,"children":804},{},[805],{"type":49,"value":806},"Email (SendGrid):",{"type":49,"value":808}," Unlimited content, rich HTML, attachments. Lowest cost. Slowest open rate. Best for receipts, summaries, non-urgent.",{"type":43,"tag":73,"props":810,"children":811},{},[812,817],{"type":43,"tag":115,"props":813,"children":814},{},[815],{"type":49,"value":816},"WhatsApp:",{"type":49,"value":818}," Rich media, interactive buttons, international reach. Requires template approval for outbound. Best for markets where WhatsApp dominates (India, Brazil, EU).",{"type":43,"tag":73,"props":820,"children":821},{},[822,827],{"type":43,"tag":115,"props":823,"children":824},{},[825],{"type":49,"value":826},"Voice:",{"type":49,"value":828}," Highest urgency signal — phone rings, demands attention. Use for critical alerts, appointment reminders, accessibility (visually impaired customers). Most expensive.",{"type":43,"tag":392,"props":830,"children":832},{"id":831},"statuscallbacks-mandatory-best-practice",[833],{"type":49,"value":834},"StatusCallbacks — Mandatory Best Practice",{"type":43,"tag":52,"props":836,"children":837},{},[838],{"type":49,"value":839},"Always inject StatusCallback URLs into every send.",{"type":43,"tag":69,"props":841,"children":842},{},[843,856,869,874],{"type":43,"tag":73,"props":844,"children":845},{},[846,848,854],{"type":49,"value":847},"SMS: StatusCallback parameter on every ",{"type":43,"tag":161,"props":849,"children":851},{"className":850},[],[852],{"type":49,"value":853},"messages.create()",{"type":49,"value":855}," call",{"type":43,"tag":73,"props":857,"children":858},{},[859,861,867],{"type":49,"value":860},"Voice: StatusCallback on ",{"type":43,"tag":161,"props":862,"children":864},{"className":863},[],[865],{"type":49,"value":866},"calls.create()",{"type":49,"value":868}," and within TwiML verbs",{"type":43,"tag":73,"props":870,"children":871},{},[872],{"type":49,"value":873},"Email: SendGrid Event Webhooks for delivery, open, click, bounce",{"type":43,"tag":73,"props":875,"children":876},{},[877],{"type":49,"value":878},"Without StatusCallbacks, you have zero visibility into delivery success.",{"type":43,"tag":392,"props":880,"children":882},{"id":881},"rate-limiting-for-notifications",[883],{"type":49,"value":884},"Rate Limiting for Notifications",{"type":43,"tag":69,"props":886,"children":887},{},[888,893,898,903],{"type":43,"tag":73,"props":889,"children":890},{},[891],{"type":49,"value":892},"Notifications are usually lower volume than marketing, but spikes happen (system alerts, mass events)",{"type":43,"tag":73,"props":894,"children":895},{},[896],{"type":49,"value":897},"Always implement 429 handling with exponential backoff (±10% jitter)",{"type":43,"tag":73,"props":899,"children":900},{},[901],{"type":49,"value":902},"Use Messaging Services even for notifications — it handles queuing and throughput optimization",{"type":43,"tag":73,"props":904,"children":905},{},[906],{"type":49,"value":907},"For Voice alerts: concurrent call limits apply. Queue calls if bursting.",{"type":43,"tag":44,"props":909,"children":911},{"id":910},"output-format",[912],{"type":49,"value":913},"Output Format",{"type":43,"tag":52,"props":915,"children":916},{},[917],{"type":49,"value":918},"After qualifying the developer, recommend:",{"type":43,"tag":656,"props":920,"children":923},{"className":921,"code":922,"language":49},[659],"Recommended Architecture: [Level 1-3 description]\n\nProduct Skills to Install:\n- twilio-sms-send-message (if SMS notifications)\n- twilio-email-send (if email notifications, Twilio creds — Account SID + Auth Token) or twilio-sendgrid-email-send (if SendGrid API key, SG.-prefix)\n- twilio-voice-outbound-calls (if voice alerts or fallback)\n- twilio-whatsapp-send-message (if WhatsApp notifications)\n- twilio-messaging-services (if volume > 100\u002Fday or multi-number)\n\nSetup Skills:\n- twilio-account-setup\n- twilio-iam-auth-setup\n- twilio-numbers-senders\n- twilio-webhook-architecture (StatusCallbacks, delivery tracking)\n\nGuardrail Skills:\n- twilio-reliability-patterns (always — backoff, retry, fallback chains)\n- twilio-security-hardening (credential management)\n- twilio-compliance-traffic (opt-out handling, quiet hours)\n",[924],{"type":43,"tag":161,"props":925,"children":926},{"__ignoreMap":664},[927],{"type":49,"value":922},{"items":929,"total":1050},[930,948,964,976,996,1018,1038],{"slug":931,"name":931,"fn":932,"description":933,"org":934,"tags":935,"stars":25,"repoUrl":26,"updatedAt":27},"accessibility-and-inclusive-visualization","make data visualizations accessible","Make data visualizations accessible and inclusive. Use when the user needs chart or diagram accessibility guidance, text alternatives for complex visuals, color and contrast review, keyboard support, reduced-motion behavior for animation or parallax, or an accessibility QA workflow for exported figures, UML-like diagrams, and dashboards.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[936,939,942,945],{"name":937,"slug":938,"type":15},"Accessibility","accessibility",{"name":940,"slug":941,"type":15},"Charts","charts",{"name":943,"slug":944,"type":15},"Data Visualization","data-visualization",{"name":946,"slug":947,"type":15},"Design","design",{"slug":949,"name":949,"fn":950,"description":951,"org":952,"tags":953,"stars":25,"repoUrl":26,"updatedAt":963},"agent-browser","automate browser interactions for agents","Browser automation CLI for AI agents. Use when the user needs to interact with websites, verify dev server output, test web apps, navigate pages, fill forms, click buttons, take screenshots, extract data, or automate any browser task. Also triggers when a dev server starts so you can verify it visually.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[954,957,960],{"name":955,"slug":956,"type":15},"Agents","agents",{"name":958,"slug":959,"type":15},"Browser Automation","browser-automation",{"name":961,"slug":962,"type":15},"Testing","testing","2026-04-06T18:41:03.44016",{"slug":965,"name":965,"fn":966,"description":967,"org":968,"tags":969,"stars":25,"repoUrl":26,"updatedAt":975},"agent-browser-verify","verify dev server output with automated browser","Automated browser verification for dev servers. Triggers when a dev server starts to run a visual gut-check with agent-browser — verifies the page loads, checks for console errors, validates key UI elements, and reports pass\u002Ffail before continuing.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[970,971,974],{"name":958,"slug":959,"type":15},{"name":972,"slug":973,"type":15},"Local Development","local-development",{"name":961,"slug":962,"type":15},"2026-04-06T18:41:17.526867",{"slug":977,"name":977,"fn":978,"description":979,"org":980,"tags":981,"stars":25,"repoUrl":26,"updatedAt":995},"agents-sdk","build AI agents on Cloudflare Workers","Build AI agents on Cloudflare Workers using the Agents SDK. Load when creating stateful agents, durable workflows, real-time WebSocket apps, scheduled tasks, MCP servers, or chat applications. Covers Agent class, state management, callable RPC, Workflows integration, and React hooks. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[982,983,986,989,992],{"name":955,"slug":956,"type":15},{"name":984,"slug":985,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":987,"slug":988,"type":15},"SDK","sdk",{"name":990,"slug":991,"type":15},"Serverless","serverless",{"name":993,"slug":994,"type":15},"WebSockets","websockets","2026-04-06T18:39:51.717063",{"slug":997,"name":997,"fn":998,"description":999,"org":1000,"tags":1001,"stars":25,"repoUrl":26,"updatedAt":1017},"ai-elements","build chat UIs with AI Elements","AI Elements component library guidance — pre-built React components for AI interfaces built on shadcn\u002Fui. Use when building chat UIs, message displays, tool call rendering, streaming responses, reasoning panels, or any AI-native interface with the AI SDK.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1002,1005,1008,1011,1014],{"name":1003,"slug":1004,"type":15},"Frontend","frontend",{"name":1006,"slug":1007,"type":15},"React","react",{"name":1009,"slug":1010,"type":15},"shadcn\u002Fui","shadcn-ui",{"name":1012,"slug":1013,"type":15},"UI Components","ui-components",{"name":1015,"slug":1016,"type":15},"Vercel","vercel","2026-04-06T18:40:59.619419",{"slug":1019,"name":1019,"fn":1020,"description":1021,"org":1022,"tags":1023,"stars":25,"repoUrl":26,"updatedAt":1037},"ai-gateway","configure Vercel AI Gateway","Vercel AI Gateway expert guidance. Use when configuring model routing, provider failover, cost tracking, or managing multiple AI providers through a unified API.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1024,1027,1030,1033,1036],{"name":1025,"slug":1026,"type":15},"AI Infrastructure","ai-infrastructure",{"name":1028,"slug":1029,"type":15},"Cost Optimization","cost-optimization",{"name":1031,"slug":1032,"type":15},"LLM","llm",{"name":1034,"slug":1035,"type":15},"Performance","performance",{"name":1015,"slug":1016,"type":15},"2026-04-06T18:40:44.377464",{"slug":1039,"name":1039,"fn":1040,"description":1041,"org":1042,"tags":1043,"stars":25,"repoUrl":26,"updatedAt":1049},"ai-generation-persistence","implement persistence patterns for AI generations","AI generation persistence patterns — unique IDs, addressable URLs, database storage, and cost tracking for every LLM generation",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1044,1045,1048],{"name":1028,"slug":1029,"type":15},{"name":1046,"slug":1047,"type":15},"Database","database",{"name":1031,"slug":1032,"type":15},"2026-04-06T18:41:08.513425",600,{"items":1052,"total":1249},[1053,1074,1097,1114,1130,1147,1166,1178,1192,1206,1218,1233],{"slug":1054,"name":1054,"fn":1055,"description":1056,"org":1057,"tags":1058,"stars":1071,"repoUrl":1072,"updatedAt":1073},"prior-auth-packet-builder","build healthcare prior authorization packets","Build a concise prior authorization packet from local case files and payer policy docs.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1059,1062,1065,1068],{"name":1060,"slug":1061,"type":15},"Documents","documents",{"name":1063,"slug":1064,"type":15},"Healthcare","healthcare",{"name":1066,"slug":1067,"type":15},"Insurance","insurance",{"name":1069,"slug":1070,"type":15},"Regulatory Compliance","regulatory-compliance",28169,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-agents-python","2026-04-16T05:11:39.180399",{"slug":1075,"name":1075,"fn":1076,"description":1077,"org":1078,"tags":1079,"stars":1094,"repoUrl":1095,"updatedAt":1096},"aspnet-core","build ASP.NET Core web applications","Build, review, refactor, or architect ASP.NET Core web applications using current official guidance for .NET web development. Use when working on Blazor Web Apps, Razor Pages, MVC, Minimal APIs, controller-based Web APIs, SignalR, gRPC, middleware, dependency injection, configuration, authentication, authorization, testing, performance, deployment, or ASP.NET Core upgrades.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1080,1083,1085,1088,1091],{"name":1081,"slug":1082,"type":15},".NET","dotnet",{"name":1084,"slug":1075,"type":15},"ASP.NET Core",{"name":1086,"slug":1087,"type":15},"Blazor","blazor",{"name":1089,"slug":1090,"type":15},"C#","csharp",{"name":1092,"slug":1093,"type":15},"Web Development","web-development",23787,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fskills","2026-04-12T05:07:02.819491",{"slug":1098,"name":1098,"fn":1099,"description":1100,"org":1101,"tags":1102,"stars":1094,"repoUrl":1095,"updatedAt":1113},"chatgpt-apps","build ChatGPT Apps SDK applications","Build, scaffold, refactor, and troubleshoot ChatGPT Apps SDK applications that combine an MCP server and widget UI. Use when Codex needs to design tools, register UI resources, wire the MCP Apps bridge or ChatGPT compatibility APIs, apply Apps SDK metadata or CSP or domain settings, or produce a docs-aligned project scaffold. Prefer a docs-first workflow by invoking the openai-docs skill or OpenAI developer docs MCP tools before generating code.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1103,1106,1109,1112],{"name":1104,"slug":1105,"type":15},"Apps SDK","apps-sdk",{"name":1107,"slug":1108,"type":15},"ChatGPT","chatgpt",{"name":1110,"slug":1111,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},"2026-04-12T05:07:05.468097",{"slug":1115,"name":1115,"fn":1116,"description":1117,"org":1118,"tags":1119,"stars":1094,"repoUrl":1095,"updatedAt":1129},"cli-creator","build CLIs from API docs","Build a composable CLI for Codex from API docs, an OpenAPI spec, existing curl examples, an SDK, a web app, an admin tool, or a local script. Use when the user wants Codex to create a command-line tool that can run from any repo, expose composable read\u002Fwrite commands, return stable JSON, manage auth, and pair with a companion skill.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1120,1123,1126],{"name":1121,"slug":1122,"type":15},"API Development","api-development",{"name":1124,"slug":1125,"type":15},"CLI","cli",{"name":1127,"slug":1128,"type":15},"Codex","codex","2026-04-12T05:07:04.132762",{"slug":1131,"name":1131,"fn":1132,"description":1133,"org":1134,"tags":1135,"stars":1094,"repoUrl":1095,"updatedAt":1146},"cloudflare-deploy","deploy projects to Cloudflare","Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1136,1139,1142,1143],{"name":1137,"slug":1138,"type":15},"Cloudflare","cloudflare",{"name":1140,"slug":1141,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":984,"slug":985,"type":15},{"name":1144,"slug":1145,"type":15},"Deployment","deployment","2026-04-12T05:07:14.275118",{"slug":1148,"name":1148,"fn":1149,"description":1150,"org":1151,"tags":1152,"stars":1094,"repoUrl":1095,"updatedAt":1165},"define-goal","define and set measurable project goals","Help the user define a concrete, measurable goal before starting work, especially when they ask to use the goal tool, create a goal, set an objective, clarify success criteria, or turn a fuzzy intention into a quantitative outcome. Use this skill for goal creation and goal refinement only; it does not manage durable snapshots, decision logs, or long-running execution artifacts.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1153,1156,1159,1162],{"name":1154,"slug":1155,"type":15},"Productivity","productivity",{"name":1157,"slug":1158,"type":15},"Project Management","project-management",{"name":1160,"slug":1161,"type":15},"Strategy","strategy",{"name":1163,"slug":1164,"type":15},"Task Management","task-management","2026-05-23T06:17:16.870838",{"slug":1167,"name":1167,"fn":1168,"description":1169,"org":1170,"tags":1171,"stars":1094,"repoUrl":1095,"updatedAt":1177},"figma","translate Figma designs into code","Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1172,1173,1175,1176],{"name":946,"slug":947,"type":15},{"name":1174,"slug":1167,"type":15},"Figma",{"name":1003,"slug":1004,"type":15},{"name":1110,"slug":1111,"type":15},"2026-04-12T05:06:47.939943",{"slug":1179,"name":1179,"fn":1180,"description":1181,"org":1182,"tags":1183,"stars":1094,"repoUrl":1095,"updatedAt":1191},"figma-code-connect-components","connect Figma designs to code components","Connects Figma design components to code components using Code Connect mapping tools. Use when user says \"code connect\", \"connect this component to code\", \"map this component\", \"link component to code\", \"create code connect mapping\", or wants to establish mappings between Figma designs and code implementations. For canvas writes via `use_figma`, use `figma-use`.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1184,1185,1188,1189,1190],{"name":946,"slug":947,"type":15},{"name":1186,"slug":1187,"type":15},"Design System","design-system",{"name":1174,"slug":1167,"type":15},{"name":1003,"slug":1004,"type":15},{"name":1012,"slug":1013,"type":15},"2026-05-10T05:59:52.971881",{"slug":1193,"name":1193,"fn":1194,"description":1195,"org":1196,"tags":1197,"stars":1094,"repoUrl":1095,"updatedAt":1205},"figma-create-design-system-rules","generate design system rules from Figma","Generates custom design system rules for the user's codebase. Use when user says \"create design system rules\", \"generate rules for my project\", \"set up design rules\", \"customize design system guidelines\", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server connection.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1198,1199,1200,1203,1204],{"name":946,"slug":947,"type":15},{"name":1186,"slug":1187,"type":15},{"name":1201,"slug":1202,"type":15},"Documentation","documentation",{"name":1174,"slug":1167,"type":15},{"name":1003,"slug":1004,"type":15},"2026-05-16T06:07:47.821474",{"slug":1207,"name":1207,"fn":1208,"description":1209,"org":1210,"tags":1211,"stars":1094,"repoUrl":1095,"updatedAt":1217},"figma-implement-design","translate Figma designs into application code","Translates Figma designs into production-ready application code with 1:1 visual fidelity. Use when implementing UI code from Figma files, when user mentions \"implement design\", \"generate code\", \"implement component\", provides Figma URLs, or asks to build components matching Figma specs. For Figma canvas writes via `use_figma`, use `figma-use`.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1212,1213,1214,1215,1216],{"name":946,"slug":947,"type":15},{"name":1174,"slug":1167,"type":15},{"name":1003,"slug":1004,"type":15},{"name":1012,"slug":1013,"type":15},{"name":1092,"slug":1093,"type":15},"2026-05-16T06:07:40.583615",{"slug":1219,"name":1219,"fn":1220,"description":1221,"org":1222,"tags":1223,"stars":1094,"repoUrl":1095,"updatedAt":1232},"hatch-pet","create animated pets for Codex","Create, repair, validate, visually QA, and package Codex-compatible animated pets and pet spritesheets from character art, generated images, company or prospect brand cues, or visual references. Use when a user wants a lightweight-worker Codex pet workflow, a non-pixel custom pet style, a prospect or company mascot pet, or a full 8x9 animated pet atlas with transparent unused cells, QA contact sheets, and pet.json packaging. This skill composes the installed $imagegen system skill for visual generation and uses bundled scripts for deterministic spritesheet assembly.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1224,1227,1228,1231],{"name":1225,"slug":1226,"type":15},"Animation","animation",{"name":1127,"slug":1128,"type":15},{"name":1229,"slug":1230,"type":15},"Creative","creative",{"name":946,"slug":947,"type":15},"2026-05-02T05:31:48.48485",{"slug":1234,"name":1234,"fn":1235,"description":1236,"org":1237,"tags":1238,"stars":1094,"repoUrl":1095,"updatedAt":1248},"imagegen","generate and edit raster images","Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG\u002Fvector\u002Fcode-native assets, extending an established icon or logo system, or building the visual directly in HTML\u002FCSS\u002Fcanvas.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1239,1240,1241,1244,1247],{"name":1229,"slug":1230,"type":15},{"name":946,"slug":947,"type":15},{"name":1242,"slug":1243,"type":15},"Image Generation","image-generation",{"name":1245,"slug":1246,"type":15},"Images","images",{"name":9,"slug":8,"type":15},"2026-05-15T06:23:24.312127",675]