convez.ai
SkillIntegração & APIsAvançado
sandeep121sandeep

Dove SMS Skill

sandeep121sandeep/dove-sms-skill

Envie SMS DLT-compliant com templates, OTP, bulk e relatórios de entrega

Ver no GitHub
InicialPluginScore · de 0 a 100

Suite de comandos `/dove-*` para enviar SMS em conformidade com DLT via Dove Soft (mobicomm), com suporte a templates aprovados, campanhas em massa, OTP/autenticação, agendamento e relatórios de entrega automáticos. Integra-se a Claude, Grok, Gemini e Codex sem dependências externas complexas.

Instalação

$npx convez-ai sandeep121sandeep/dove-sms-skill

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
42%
Último commit
há 5 meses
Versão
—
Issues abertas
0
Contribuidores
1

Casos de uso

  • Enviar campanhas promocionais em massa com rastreamento de entrega
  • Gerar e validar OTP/tokens de autenticação para usuários
  • Agendar envios de SMS para datas/horários específicos
  • Consultar e decodificar relatórios de entrega com motivos de falha
  • Gerenciar templates DLT aprovados e resolver erros de conformidade

Veredito

Ferramenta especializada e bem-engenharia para operadores SMS em India, com tratamento profundo das armadilhas da API Dove/DLT. Exige conhecimento prévio de regulamentação DLT e configuração no portal do operador, mas elimina horas de integração manual uma vez instalada.

README

A tradução para o português deste README ainda está na fila.

dove-sms-skill

A suite of /dove-* agent commands for sending DLT-compliant SMS through Dove Soft (mobicomm) — and getting the delivery report back, automatically.

Install into Claude, Grok, Gemini, or Codex. Then just say:

"Send the Diwali offer to these 400 numbers" · "Send an OTP to 98765xxxxx" · "Schedule the sale SMS for tomorrow 10am" · "Did my campaign deliver?"

The agent finds the right approved DLT template, sends on the correct route, polls the delivery report, and tells you "delivered 387/400" — with a breakdown of every failure (DND, CTA not whitelisted, template mismatch) and how to fix it.

One dependency-light Python engine (dove.py), no SDK, no server.


The /dove-* commands

CommandDoes
/dove-setupOne-time: capture API creds + import your approved DLT templates from the portal xlsx
/dove-sendSend a template to one/few numbers, confirm delivery per number
/dove-bulkBulk campaign from a list/file — dedupe, throttle, dry-run, confirm, delivered/failed breakdown
/dove-authAuthentication/OTP — generate + send + verify (your template, or Dove-native OTP)
/dove-scheduleSchedule a send or campaign for a future date/time
/dove-reportFetch + decode delivery reports (reason → DLT error code)
/dove-templatesList / inspect / import DLT templates
/dove-errorsDLT error-code lookup with fixes

Why this exists

The Dove/DLT API has sharp edges that cost hours. This suite bakes the fixes in:

  • The content parameter is message, not msg. Send msg alone and the operator returns 633 "DLT Template Not Matched" because the body arrives blank. (We always send both.)
  • mobile must have no leading + on submitsms.jsp.
  • The delivery-report endpoint is incremental — only returns un-downloaded reports unless redownload=yes (capped at 7). We default it on. Its messageid filter matches the batch id, not the numeric id.
  • Promotional route (accusage=2) respects DND (blocked_ndnc / 004) and needs every URL/email/phone CTA whitelisted in DLT (codes 700–703).
  • A gateway sent,success is accepted, not delivered — you must read the DLR. We do.

The full DLT error-code table ships in errorcodes.json.


Prerequisite — DLT registration (do this first)

This tool delivers SMS; it can't create DLT registrations. Indian SMS only goes out if the content is pre-approved on your DLT operator portal (Smartping / Jio / Airtel / BSNL). Before your first send you need, once:

  • an approved header (sender ID),
  • at least one approved content template,
  • a live PE-TM chain (telemarketer = Dove Soft linked to your PEID) — else 813,
  • a whitelisted CTA for any URL in a promo template — else 700/701.

👉 Step-by-step (Smartping, with the other operators noted): docs/DLT-SETUP.md. Once everything is Approved/Active, export your template-dump xlsx and run /dove-setup.


Install

git clone https://github.com/sandeep121sandeep/dove-sms-skill.git
cd dove-sms-skill
pip install -r requirements.txt           # optional: openpyxl (xlsx) + certifi (TLS)

./install/dovesoft.sh                       # -> ~/.claude/skills (Claude)
# Codex:  ./install/dovesoft.sh ~/.codex/skills

Each /dove-* skill is installed self-contained (its own engine copy), so after you pull a repo update, re-run ./install/dovesoft.sh to refresh the copies. Then:

/dove-setup        # or: python3 ~/.claude/skills/dove-setup/dove.py init --user <U> --key <K> --entityid <PEID>

/dove-setup also imports your approved templates from your DLT template-dump xlsx.

Notes: Mobile numbers are 10-digit Indian mobiles without a leading + or country code (the tool strips +). Template keys are slugs of the DLT Template Name — run /dove-templates to see the exact --name values after import.

Other hosts

AGENTS.md is the host-agnostic resolver (Grok, Gemini, Codex, any shell-capable agent). SKILL.md files target Claude. The engine is identical everywhere.


Configuration

Credentials and templates live in one shared file:

~/.dove/config.json          # chmod 600, used by every /dove-* command

Resolution order: $DOVE_CONFIG → ~/.dove/config.json → ./config.json (local dev). Only config.example.json (placeholders) ships in the repo; real config is git-ignored.

Manage the engine directly anytime:

dove init        --user --key --entityid          # create config
dove doctor                                        # validate config + connectivity
dove templates   [--xlsx PATH [--save]]            # list / import templates
dove send-template --name --mobile [--otp] [--schedule "YYYY-MM-DD HH:MM:SS"]
dove send-smart  --name --to N1,N2 [--otp] --date YYYY-MM-DD
dove bulk        --name (--to|--file) [--otp] [--rate S] [--schedule ...] [--dry-run] --yes --date YYYY-MM-DD
dove report      --date YYYY-MM-DD [--messageid BATCH]
dove otp-gen     --mobile --ttl --message "...{otp}..."   # Dove native OTP
dove otp-verify  --otp --mobile [--otpid]
dove gencode     [--digits 6]                      # CSPRNG OTP code
dove errors      [CODE] ; dove routes

Routes (accusage)

RouteaccusageDNDNotes
Transactional1reaches DNDOTP/alerts ride here fine
Promotional2respects DND (004/333)URLs need CTA whitelisting (700–703)
International3—
OTP6reaches DNDdedicated OTP route
RCS7—
WhatsApp10—

Security

  • Your API key lives only in ~/.dove/config.json (chmod 600), outside the repo and git-ignored. Skill installs copy the engine per skill, never the credentials.
  • The CLI reads the key from config — never put it on a command line in shared logs.
  • dove doctor prints your username + PEID (never the key) for diagnostics — avoid pasting its raw output into public threads if those are sensitive.
  • This tool sends real SMS that cost money and are regulated (TRAI/DLT in India). You are responsible for consent and content compliance. Promotional sends to DND numbers are blocked by design; bulk sends require explicit --yes.

License

MIT — see LICENSE.

Not affiliated with or endorsed by Dove Soft Ltd. "Dove Soft" / mobicomm are referenced for interoperability only.

Ver o original no GitHub

Bom para

Relacionados