Telecom Agent Skill

Turn your AI Agent into a Telecom Operator. Bulk calling, ChatOps, and Field Monitoring.

Security Scan

The skill claims to operate telephony (Twilio) and Telegram remote admin but provides no declared credentials or safe install mechanism and gives vague runtime instructions — this mismatch is suspicious and needs clarification before installation.

Purpose & Capability

The skill advertises Twilio onboarding, dialing, recordings, and Telegram admin, but the registry metadata lists no required environment variables, primary credential, or config paths. A legitimate telecom integration would normally require provider credentials (e.g., Twilio SID/Token) and API tokens for Telegram; their absence is an incoherence.

Instruction Scope

SKILL.md instructs the agent to run an installation command and then use a 'telecom' CLI (telecom onboard, campaign create, call, memory) that isn't supplied by the registry entry. It also instructs uploading large lists, making calls, recording audio, and reading transcripts — sensitive operations with unclear data flows or destination endpoints (Operator Console is unnamed). Instructions are vague about where data goes and grant broad discretion to install/run external code.

Install Mechanism

There is no formal install spec in the registry, yet the SKILL.md tells the user/agent to run '/install https://github.com/kflohr/telecom-agent-skill'. That is an out-of-band download-and-run instruction with no checksum, release tag, or provenance; installing arbitrary code from an external GitHub repo without verification is a high-risk pattern.

Credentials

The skill's behavior clearly requires telephony and Telegram credentials and will handle sensitive PII (phone lists, call recordings, transcripts), but it requests no environment variables or tokens in the registry metadata. This under-declaration prevents reviewers from assessing the scope of credentials the skill will use and is disproportionate to the metadata provided.

Persistence & Privilege

The skill does not request 'always: true' and declares no config paths, which is appropriate. However, autonomous invocation is allowed by default and, combined with telephony capabilities and an unverified install, increases potential blast radius — confirm runtime controls and approval workflows before enabling.

What to consider before installing

Do not install this skill yet. It claims to connect to Twilio and Telegram and to install a 'telecom' CLI, but the registry entry provides no credentials, no verified install method, and no details about where call data/transcripts are stored or who controls the Operator Console. Ask the publisher for: (1) a verified source URL and release/tag plus checksum or signed release; (2) an explicit list of required environment variables (Twilio SID/Token, Telegram Bot token, etc.); (3) a privacy/data-retention statement for call recordings and transcripts and whether consent/opt-out is handled; (4) limited-permission example credentials or a sandbox account for testing; and (5) the actual code for review. If you must test, use an isolated environment and non-production/test telephony accounts, restrict network access, and review the repository content before running any install command.

📡 Telecom Agent Skill v1.2

Give your MoltBot / OpenClaw agent the power of a Telecom Operator.

This skill connects your agent to the Telecom Operator Console, allowing it to manage campaigns, handle approvals, and operate on the public telephone network safely.

✨ Capabilities

🚀 Campaign Queue (Bulk Calling) New

• Mass Dialing: Upload a list of 10,000+ numbers. The system handles rate-limiting.
• ChatOps: "Bot, create a campaign for the 'Friday Leads' list."
• Monitoring: Agent can poll status with --json for precise progress tracking.

🗣️ Voice & Speech

• Make Calls: Dial any global number.
• Speak: Dynamic "Text-to-Speech" intro messages.
• Listen: Records audio automatically for quality assurance.

📱 Field Operations (Telegram)

• Remote Admin: Monitor system status from a Telegram Bot.
• Approvals: Approve/Deny high-risk actions via mobile buttons.

🧠 Operational Memory

• Transcripts: Agent can read full call transcripts (telecom agent memory).
• Persistence: All logs saved to the secure Operator Console.

---

🚀 Quick Start for Agents

1. Installation

/install https://github.com/kflohr/telecom-agent-skill

2. Setup

telecom onboard
# Follow the wizard to link your Twilio account.

3. Usage Examples

Bulk Campaign:

telecom campaign create "Outreach" --file leads.csv
telecom campaign status <id> --json

Single Call:

telecom agent call [phone] --intro "Hello from the AI team."

Memory Retrieval:

telecom agent memory <CallSid>