ClickSend

**Judgement:** This is a strong, fairly complete ClickSend integration for SMS/MMS/voice and contact/list management, suitable for production-style messaging workflows if you already rely on ClickSend via Maton. **What it does well** - Exposes most essential ClickSend v3 capabilities: send SMS/MMS/voice, check prices, manage templates, contacts, and lists, plus history and receipts. - Uses Maton’s managed authentication and connection objects, which keeps raw ClickSend credentials out of your code/skills and simplifies multi-account setups. - Documentation is detailed and practical (endpoints, parameters, examples, pagination, error handling, and troubleshooting), so it should be straightforward to implement typical flows. **Key risks / limitations** - **External dependencies:** Requires both Maton (gateway.maton.ai / ctrl.maton.ai) and ClickSend services to be available; any outage or auth misconfiguration will break messaging. - **Compliance and abuse risk:** Enables bulk messaging and voice calls; you must handle legal/compliance aspects (e.g., spam, opt-in/opt-out, TCPA/GDPR equivalents) and avoid harassment or fraud use-cases. - **Cost and rate limiting:** SMS/MMS/voice can be expensive at scale and are subject to ClickSend rate limits; the skill does not itself enforce cost caps or throttling. - **Channel scope:** Focused on ClickSend’s messaging stack; for other third-party APIs you’re expected to use the separate `api-gateway` skill. **Recommended scenarios** - You already have (or are willing to set up) a Maton account with a ClickSend connection and want a single skill to handle SMS/MMS/voice plus contacts/lists. - You need reliable transactional SMS or voice alerts (2FA, incident notifications, order status) with delivery receipts and price checks. - You want to orchestrate campaign-style messaging against ClickSend contact lists, using templates and personalization, while managing opt-out lists yourself. - You’re comfortable managing compliance, costs, and correct E.164 formatting, and you accept dependency on Maton + ClickSend infrastructure.

**Judgment** A solid, well-scoped integration for ClickSend that uses Maton as a managed gateway. It appears technically coherent and matches its description, with broad coverage of core ClickSend features (SMS, MMS, voice, contacts, lists, and pricing) and very clear usage instructions. **Key Risks** - **Data exposure to Maton:** All traffic (message content, phone numbers, contact data, account info) is proxied through `maton.ai`. You must trust Maton’s security and privacy posture and be comfortable with this additional party accessing your messaging data. - **Extra dependency:** Availability now depends on both ClickSend and Maton; outages or changes in either service can affect reliability. - **Regulatory/compliance:** As with any messaging integration, you are responsible for complying with SMS/voice regulations (e.g., consent, opt-outs, data protection) in your jurisdiction. **Recommended Scenarios** Use this skill when you: - Already use or plan to use **ClickSend** for SMS/MMS/voice and want the assistant to send messages or manage contacts on your behalf. - Prefer **not** to handle ClickSend credentials directly and are willing to rely on a **single Maton API key** and the Maton proxy. - Need multi-channel messaging (SMS, MMS, voice) plus contact/list management from within OpenClaw. If you want to integrate with **other third-party apps** (not ClickSend), prefer the separate `api-gateway` skill as suggested by the author.