Send SMS text and bulk messages via TelTel.io API

ReviewAudited by ClawScan on May 10, 2026.

Overview

This is a transparent TelTel SMS helper, but it can use your TelTel API key to send paid single or bulk texts.

This skill appears purpose-aligned and transparent. Install it only if you intend to let OpenClaw send SMS through your TelTel account, protect the API key, keep the default API URL unless you know why you are changing it, and use dry-run or manual confirmation for bulk messages.

Findings (2)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

If invoked with the wrong recipients or message, the skill could send unwanted texts or incur TelTel charges.

Why it was flagged

The script can send bulk SMS messages through the provider API. This matches the skill purpose, but it is a real-world side effect that can contact many recipients and may use account credit.

Skill content
const url = `${BASE_URL}/sms/bulk/text`; ... const res = await fetch(url, { method: 'POST', ... body: JSON.stringify(payload), });
Recommendation

Use dry-run first for bulk sends, confirm the recipient list and message content, and avoid letting the agent send messages without clear user approval.

What this means

Anyone with the API key may be able to send SMS through the user's TelTel account, and an untrusted API endpoint could receive the key if configured.

Why it was flagged

The script authenticates to TelTel with an API key and sends that key to the configured base URL. This is expected for the integration, but a custom base URL or command-line API key use should be handled carefully.

Skill content
const BASE_URL = process.env.TELTEL_BASE_URL || 'https://api.teltel.io/v2'; ... const apiKey = args.apikey || process.env.TELTEL_API_KEY; ... 'x-api-key': apiKey
Recommendation

Store the API key in the OpenClaw skill credential field or environment, do not share it in chat or shell history, and leave TELTEL_BASE_URL at the default unless the alternate endpoint is trusted.