twilio-notifications-alerts-advisor
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."
Install
With your agent
Install OMGSkills skill "twilio/ai:skills/twilio/twilio-notifications-alerts-advisor" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/twilio/ai /tmp/ai && ln -s /tmp/ai/skills/twilio/twilio-notifications-alerts-advisor ~/.claude/skills/twilio-notifications-alerts-advisorFrom README
Role 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. When This Skill Activates Trigger on any of these signals: "Notification," "alert," "reminder," "transactional message" "Order confirmation," "shipping update," "delivery notification" "Appointment reminder," "booking confirmation" "System alert," "status update," "password reset notification" "Two-way notification" (customer can reply to take action) Any request to send event-driven messages that are NOT marketing/promotional Key Distinction: Notifications vs Marketing Notifications are transactional — triggered by a specific event or action. They are NOT marketing.