sms-best-practicesProvides SMS compliance, formatting, and delivery best practices for the Sendly API. Covers TCPA compliance, quiet hours, opt-out handling, E.164 phone forma...
Install via ClawdBot CLI:
clawdbot install sendly-live/sms-best-practicesGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://sendly.live/docs/concepts/complianceAudited Apr 16, 2026 · audit v1.0
Generated Jul 9, 2026
An online store sends transactional SMS confirmation after a purchase. Using E.164 format and proper message type ensures compliance with TCPA and avoids quiet hours restrictions.
A restaurant runs a marketing campaign for lunch specials. They must obtain prior consent, respect quiet hours, and include opt-out instructions to avoid TCPA fines.
A clinic sends transactional reminders to patients. Since it's transactional, it's allowed 24/7, but must format phone numbers in E.164 and ensure SHAFT compliance.
A fintech app sends OTP codes transactionally. They must use E.164 formatting, handle opt-outs automatically, and keep messages under segmentation limits for reliability.
A nonprofit sends marketing SMS for a fundraising campaign. They need consent, avoid quiet hours, and follow SHAFT filters to prevent content violations.
Agencies manage campaigns for multiple clients, leveraging Sendly's API for compliance and delivery. Revenue comes from monthly retainers or per-campaign fees.
SaaS products integrate Sendly for transactional alerts (e.g., booking confirmations). Charged as subscription add-on or usage-based credits.
Online stores use SMS for order updates and promotions. Costs per message segment affect margins; revenue increases via higher conversion from SMS marketing.
💬 Integration Tip
Start by formatting all phone numbers as E.164 using a library like libphonenumber, and always set the message type correctly (transactional vs marketing) to avoid compliance issues.
Scored Jul 9, 2026
Control desktop applications on Windows — launch, close, focus, resize, move windows, simulate keyboard/mouse input, manage processes, control VSCode, read clipboard, and capture screen info. Use when the user wants to interact with any running program, switch windows, type text, press shortcuts, open files in VSCode, manage running processes, or get system display information.
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
Coding style memory that adapts to your preferences, conventions, and patterns for consistent coding.
Pragmatic coding standards for writing clean, maintainable code — naming, functions, structure, anti-patterns, and pre-edit safety checks. Use when writing new code, refactoring existing code, reviewing code quality, or establishing coding standards.
Claude Code integration for OpenClaw. This skill provides interfaces to: - Query Claude Code documentation from https://code.claude.com/docs - Manage subagents and coding tasks - Execute AI-assisted coding workflows - Access best practices and common workflows Use this skill when users want to: - Get help with coding tasks - Query Claude Code documentation - Manage AI-assisted development workflows - Execute complex programming tasks
Plan, draft, version, and refine written content with enforced versioning and quality audits.