[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVZ5EMZ8ZME6V9B3N4FS9W":3,"skill-same:01M7EVZ5EMZ8ZME6V9B3N4FS9W":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EVZ5EMZ8ZME6V9B3N4FS9W","sms-pro",null,"Use SMS professionally — business texting etiquette, alerts, 2FA-adjacent flows, and compliant organizational messaging.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-sms-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sms-pro\ndescription: Use SMS professionally — business texting etiquette, alerts, 2FA-adjacent flows, and compliant organizational messaging.\ncategory: enterprise-communication\n---\n\n## Overview\n\nSMS in professional contexts means transactional and operational messaging: alerts, reminders, coordination, and time-sensitive notifications — not marketing blasts (see sms-marketer for that). This skill covers business texting: etiquette, alert design, automation, and the compliance basics for organizational SMS.\n\n\nProfessional SMS — appointment reminders, delivery updates, authentication codes, urgent alerts — reaches people faster than any other channel: 90%+ read within minutes. That speed makes it ideal for time-critical operational messaging and terrible for anything that can wait. The skill is reserving SMS for moments where immediacy genuinely matters.\n## When to use\n\n- Setting up operational SMS alerts\n- Writing appointment\u002Fservice reminders\n- Coordinating teams via text\n- Designing notification SMS (deliveries, incidents, system alerts)\n- Establishing business texting policies\n- Choosing SMS for internal vs. external comms\n\n- Appointment reminders and confirmations\n- Two-factor authentication and security alerts\n- Urgent operational notifications (outages, delays)\n- Implementing SMS APIs for developers\n- Building international SMS coverage\n- Choosing SMS providers\n## Core concepts\n\n**SMS role in the mix.** SMS is for: time-sensitive alerts, reminders, short coordination, and 2FA\u002Fverification codes. It's not for: long discussions (use email\u002Fchat), sensitive data (use secure channels), or anything non-urgent (respect the interruption).\n\n**Alert design.** Critical alerts: what happened, impact, what to do, where to go — in 160 characters. Include severity, avoid jargon, link to details. Alert fatigue is real: only truly actionable items via SMS; everything else via less intrusive channels.\n\n**Reminders.** Appointment\u002Fservice reminders: who, what, when, where, how to confirm\u002Fcancel\u002Freschedule. Send at useful intervals (24h + 2h typical). Two-way (reply C to confirm) dramatically reduces no-shows.\n\n**Business texting etiquette.** Identify yourself\u002Forganization, keep it brief, respect hours (no non-urgent texts outside business hours), one topic per message, and provide an opt-out path. Professional tone — texts feel personal, so sloppiness stands out.\n\n**Automation.** Triggered SMS from systems: monitoring alerts, scheduling systems, delivery updates, incident notifications. Build in: deduplication (don't send the same alert 50 times), escalation (unacknowledged → next person), and quiet hours with critical-override rules.\n\n**Compliance basics.** Consent for non-transactional messages, opt-out honoring (STOP), sender identification, and data retention policies. Transactional messages (alerts the user signed up for) have lighter requirements than promotional — but document consent either way. Consult legal for your jurisdiction.\n\n\n**Transactional vs. promotional.** Transactional SMS (order updates, codes, alerts) enjoys high tolerance because it is expected and useful. Promotional SMS faces strict consent requirements and low tolerance. Never blur the line — sending marketing in transactional streams triggers complaints and regulatory risk.\n\n**Sender identity.** Short codes (5–6 digits, high throughput, expensive), long codes \u002F 10DLC (standard numbers, conversational, US carrier-registered), and alphanumeric sender IDs (international, one-way). Choose by use case: 10DLC for conversational business texting, short codes for high-volume alerts, toll-free for support lines.\n\n**Quiet hours and frequency.** Even transactional messages respect local quiet hours (typically 8am–9pm). Frequency expectations: authentication = instant, appointments = 24h + 2h reminders, alerts = only when actionable. Every unnecessary text trains recipients to ignore the necessary ones.\n\n**Provider selection.** Evaluate: delivery rates by country, latency, pricing (per-segment, not per-message — segments matter), API quality, support responsiveness, and compliance features.\nTest with real traffic before committing — provider performance varies enormously by destination.\nMulti-provider setups hedge outages but add complexity.\n**Encoding and segmentation.** GSM-7 (160 chars\u002Fsegment) vs. Unicode (70 chars\u002Fsegment) — emojis and non-Latin scripts triple costs.\nConcatenate carefully; long messages cost multiples.\nCharacter counters in composing UIs prevent surprise bills.\n**Delivery monitoring.** Delivery receipts (DLRs), latency tracking, failure categorization (invalid number, carrier block, content filter), and retry logic.\nMonitor by destination — country-level issues hide in global averages.\nAlert on delivery drops; they indicate blocks or outages.\n## Practical workflow\n\n1. **Define use cases.** List what merits SMS: incident alerts, appointment reminders, delivery notifications, shift coordination, verification codes. Everything else uses other channels.\n2. **Design message templates.** Per use case: concise template with variables, severity levels for alerts, and clear CTAs. Test readability — if it needs scrolling, it's too long.\n3. **Set policies.** Quiet hours, opt-in\u002Fopt-out handling, who can send broadcast texts, tone guidelines, and data retention. Publish the policy.\n4. **Build automation.** Integrate with source systems (monitoring, scheduling, ticketing). Implement: dedup, escalation chains, acknowledgment tracking, and delivery logging.\n5. **Launch carefully.** Start with transactional use cases (lowest risk, highest value). Monitor: delivery rates, opt-out rates, response times, and complaint feedback.\n6. **Review.** Monthly: are alerts actionable? (If routinely ignored, they're noise — fix or remove.) Opt-out trends, after-hours volume, and user feedback.\n\n**Incident alert template:** \"[SEV2] Payment API error rate 15% (threshold 5%). Dashboard: [link]. Ack: reply ACK. On-call: [name].\"\n\n\n**Appointment reminder sequence:** T-48h: confirmation request (reply YES to confirm) → T-24h: reminder with details (time, location, preparation) → T-2h: final nudge with check-in link. No-show rates typically drop 30–50% with this sequence. Include reschedule links — friction-free rescheduling beats no-shows.\n\n**2FA SMS best practices:** 6-digit codes (memorable, auto-fillable) → 5–10 minute expiry → clear sender identification → \"never share this code\" warning → rate-limit requests (prevent SMS bombing) → offer authenticator-app alternatives. Monitor delivery rates by carrier — SMS 2FA fails silently on some networks.\n\n**API integration checklist:** credentials secured → webhook endpoints for DLRs → retry logic with backoff → number validation pre-send → opt-out list syncing → rate limiting → test numbers across carriers → monitoring dashboards.\nLoad-test before campaigns — provider rate limits surprise the unprepared.\n**Cost optimization:** validate numbers (remove landlines, invalid) → use correct encoding → batch where possible → negotiate volume pricing → monitor per-campaign costs.\nSMS costs scale linearly — 10% waste reduction is real money at volume.\n## Common pitfalls\n\n- **Alert fatigue.** SMS for everything means SMS for nothing. Reserve for actionable and urgent.\n- **No dedup.** 47 identical alerts at 3am. Deduplicate and escalate instead.\n- **After-hours non-urgent texts.** Respect quiet hours; use scheduled sends for morning delivery.\n- **Missing opt-out.** No way to stop messages. Always provide and honor opt-out.\n- **Sensitive data via SMS.** Passwords, full account numbers, health details — SMS isn't secure. Use it for pointers, not payloads.\n- **No acknowledgment tracking.** Sending critical alerts into the void. Track acks; escalate silence.\n- **Inconsistent sender identity.** Messages from random numbers. Use consistent, identified sender IDs.\n- **Using SMS for non-urgent content.** Newsletters via text. Reserve SMS for immediacy — everything else belongs in email or push.\n- **No opt-out handling.** Failing to process STOP requests immediately. Regulatory penalties are severe and per-message.\n- **Ignoring international complexity.** Sender ID rules, character encoding (GSM vs. Unicode segment limits), and pricing vary wildly by country. Test per market.\n- **No DLR handling.** Sending blind without delivery confirmation. DLRs are the only truth about delivery — process them.\n- **Single provider dependency.** Provider outages halt all messaging. Critical flows deserve failover providers.\n","## Overview\n\nSMS in professional contexts means transactional and operational messaging: alerts, reminders, coordination, and time-sensitive notifications — not marketing blasts (see sms-marketer for that). This skill covers business texting: etiquette, alert design, automation, and the compliance basics for organizational SMS.\n\n\nProfessional SMS — appointment reminders, delivery updates, authentication codes, urgent alerts — reaches people faster than any other channel: 90%+ read within minutes. That speed makes it ideal for time-critical operational messaging and terrible for anything that can wait. The skill is reserving SMS for moments where immediacy genuinely matters.\n## When to use\n\n- Setting up operational SMS alerts\n- Writing appointment\u002Fservice reminders\n- Coordinating teams via text\n- Designing notification SMS (deliveries, incidents, system alerts)\n- Establishing business texting policies\n- Choosing SMS for internal vs. external comms\n\n- Appointment reminders and confirmations\n- Two-factor authentication and security alerts\n- Urgent operational notifications (outages, delays)\n- Implementing SMS APIs for developers\n- Building international SMS coverage\n- Choosing SMS providers\n## Core concepts\n\n**SMS role in the mix.** SMS is for: time-sensitive alerts, reminders, short coordination, and 2FA\u002Fverification codes. It's not for: long discussions (use email\u002Fchat), sensitive data (use secure channels), or anything non-urgent (respect the interruption).\n\n**Alert design.** Critical alerts: what happened, impact, what to do, where to go — in 160 characters. Include severity, avoid jargon, link to details. Alert fatigue is real: only truly actionable items via SMS; everything else via less intrusive channels.\n\n**Reminders.** Appointment\u002Fservice reminders: who, what, when, where, how to confirm\u002Fcancel\u002Freschedule. Send at useful intervals (24h + 2h typical). Two-way (reply C to confirm) dramatically reduces no-shows.\n\n**Business texting etiquette.** Identify yourself\u002Forganization, keep it brief, respect hours (no non-urgent texts outside business hours), one topic per message, and provide an opt-out path. Professional tone — texts feel personal, so sloppiness stands out.\n\n**Automation.** Triggered SMS from systems: monitoring alerts, scheduling systems, delivery updates, incident notifications. Build in: deduplication (don't send the same alert 50 times), escalation (unacknowledged → next person), and quiet hours with critical-override rules.\n\n**Compliance basics.** Consent for non-transactional messages, opt-out honoring (STOP), sender identification, and data retention policies. Transactional messages (alerts the user signed up for) have lighter requirements than promotional — but document consent either way. Consult legal for your jurisdiction.\n\n\n**Transactional vs. promotional.** Transactional SMS (order updates, codes, alerts) enjoys high tolerance because it is expected and useful. Promotional SMS faces strict consent requirements and low tolerance. Never blur the line — sending marketing in transactional streams triggers complaints and regulatory risk.\n\n**Sender identity.** Short codes (5–6 digits, high throughput, expensive), long codes \u002F 10DLC (standard numbers, conversational, US carrier-registered), and alphanumeric sender IDs (international, one-way). Choose by use case: 10DLC for conversational business texting, short codes for high-volume alerts, toll-free for support lines.\n\n**Quiet hours and frequency.** Even transactional messages respect local quiet hours (typically 8am–9pm). Frequency expectations: authentication = instant, appointments = 24h + 2h reminders, alerts = only when actionable. Every unnecessary text trains recipients to ignore the necessary ones.\n\n**Provider selection.** Evaluate: delivery rates by country, latency, pricing (per-segment, not per-message — segments matter), API quality, support responsiveness, and compliance features.\nTest with real traffic before committing — provider performance varies enormously by destination.\nMulti-provider setups hedge outages but add complexity.\n**Encoding and segmentation.** GSM-7 (160 chars\u002Fsegment) vs. Unicode (70 chars\u002Fsegment) — emojis and non-Latin scripts triple costs.\nConcatenate carefully; long messages cost multiples.\nCharacter counters in composing UIs prevent surprise bills.\n**Delivery monitoring.** Delivery receipts (DLRs), latency tracking, failure categorization (invalid number, carrier block, content filter), and retry logic.\nMonitor by destination — country-level issues hide in global averages.\nAlert on delivery drops; they indicate blocks or outages.\n## Practical workflow\n\n1. **Define use cases.** List what merits SMS: incident alerts, appointment reminders, delivery notifications, shift coordination, verification codes. Everything else uses other channels.\n2. **Design message templates.** Per use case: concise template with variables, severity levels for alerts, and clear CTAs. Test readability — if it needs scrolling, it's too long.\n3. **Set policies.** Quiet hours, opt-in\u002Fopt-out handling, who can send broadcast texts, tone guidelines, and data retention. Publish the policy.\n4. **Build automation.** Integrate with source systems (monitoring, scheduling, ticketing). Implement: dedup, escalation chains, acknowledgment tracking, and delivery logging.\n5. **Launch carefully.** Start with transactional use cases (lowest risk, highest value). Monitor: delivery rates, opt-out rates, response times, and complaint feedback.\n6. **Review.** Monthly: are alerts actionable? (If routinely ignored, they're noise — fix or remove.) Opt-out trends, after-hours volume, and user feedback.\n\n**Incident alert template:** \"[SEV2] Payment API error rate 15% (threshold 5%). Dashboard: [link]. Ack: reply ACK. On-call: [name].\"\n\n\n**Appointment reminder sequence:** T-48h: confirmation request (reply YES to confirm) → T-24h: reminder with details (time, location, preparation) → T-2h: final nudge with check-in link. No-show rates typically drop 30–50% with this sequence. Include reschedule links — friction-free rescheduling beats no-shows.\n\n**2FA SMS best practices:** 6-digit codes (memorable, auto-fillable) → 5–10 minute expiry → clear sender identification → \"never share this code\" warning → rate-limit requests (prevent SMS bombing) → offer authenticator-app alternatives. Monitor delivery rates by carrier — SMS 2FA fails silently on some networks.\n\n**API integration checklist:** credentials secured → webhook endpoints for DLRs → retry logic with backoff → number validation pre-send → opt-out list syncing → rate limiting → test numbers across carriers → monitoring dashboards.\nLoad-test before campaigns — provider rate limits surprise the unprepared.\n**Cost optimization:** validate numbers (remove landlines, invalid) → use correct encoding → batch where possible → negotiate volume pricing → monitor per-campaign costs.\nSMS costs scale linearly — 10% waste reduction is real money at volume.\n## Common pitfalls\n\n- **Alert fatigue.** SMS for everything means SMS for nothing. Reserve for actionable and urgent.\n- **No dedup.** 47 identical alerts at 3am. Deduplicate and escalate instead.\n- **After-hours non-urgent texts.** Respect quiet hours; use scheduled sends for morning delivery.\n- **Missing opt-out.** No way to stop messages. Always provide and honor opt-out.\n- **Sensitive data via SMS.** Passwords, full account numbers, health details — SMS isn't secure. Use it for pointers, not payloads.\n- **No acknowledgment tracking.** Sending critical alerts into the void. Track acks; escalate silence.\n- **Inconsistent sender identity.** Messages from random numbers. Use consistent, identified sender IDs.\n- **Using SMS for non-urgent content.** Newsletters via text. Reserve SMS for immediacy — everything else belongs in email or push.\n- **No opt-out handling.** Failing to process STOP requests immediately. Regulatory penalties are severe and per-message.\n- **Ignoring international complexity.** Sender ID rules, character encoding (GSM vs. Unicode segment limits), and pricing vary wildly by country. Test per market.\n- **No DLR handling.** Sending blind without delivery confirmation. DLRs are the only truth about delivery — process them.\n- **Single provider dependency.** Provider outages halt all messaging. Critical flows deserve failover providers.\n",{"name":5,"category":24,"description":7},"enterprise-communication","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-sms-pro",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill sms-pro",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill sms-pro",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill sms-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-sms-pro\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]