← Back to Skills Marketplace
5289
Downloads
2
Stars
17
Active Installs
15
Versions
Install in OpenClaw
/install clawdtalk-client
Description
ClawdTalk — Voice calls, SMS, and AI Missions for Clawdbot
Usage Guidance
Review carefully before installing. Use it only if you trust ClawdTalk/Telnyx with call transcripts, SMS content, mission data, and a persistent bridge into your main OpenClaw agent. Prefer environment variables or a secret store for keys, avoid custom server URLs unless you control them, restrict the agent tools available to voice/SMS sessions where possible, and do not rely on the built-in approval flow for destructive or financial actions without an independent confirmation step.
Capability Analysis
Type: OpenClaw Skill
Name: clawdtalk-client
Version: 2.0.5
This skill is classified as suspicious due to several high-risk capabilities and vulnerabilities, despite being extensively documented. The `setup.sh` script, guided by `SETUP.md` instructions for the AI agent, modifies the host system's `gateway.tools.allow` configuration to permit `sessions_send`. This grants the `ws-client.js` (and by extension, the remote ClawdTalk service) the ability to send arbitrary messages to the local agent's main session, effectively allowing remote control of the agent's actions. Furthermore, the `ws-client.js`'s `DEFAULT_VOICE_CONTEXT` instructs the AI agent to accept voice confirmations for sensitive actions, potentially bypassing more secure push notification/biometric approvals. While these actions are disclosed in the documentation and some require confirmation during setup, the combination of powerful capabilities, a direct instruction to the agent to enable them, and a weakened approval mechanism constitutes a significant security risk.
Capability Assessment
Purpose & Capability
Voice calls, SMS, outbound calls, and mission tracking fit the stated purpose, and the docs disclose ClawdTalk/Telnyx data flows. The concern is that voice, SMS, and walkie-talkie inputs are routed into the main agent session with full tool context, while examples cover destructive, financial, and public-posting actions beyond a narrow communications client.
Instruction Scope
The runtime prompt tells the agent it has full tool access during calls, the code prepends an instruction telling the downstream agent not to request approval, and no-device approval cases can still route sensitive requests onward. This is under-scoped for high-impact actions initiated from phone/SMS input.
Install Mechanism
Setup is interactive and asks before adding sessions_send, but it changes gateway.tools.allow, copies the gateway token into skill-config.json, stores the ClawdTalk API key locally, installs npm dependencies, and has a runtime npm install fallback that is not accurately reflected by the ws-client header.
Credentials
A persistent WebSocket to clawdtalk.com is expected for the service, but it transmits call/SMS content and allows remote events to drive local gateway sessions_send requests into the user's primary agent context.
Persistence & Privilege
The skill starts a background process, writes PID/log/state/config files, supports watchdog restarts, and encourages cron-based polling for missions. These are mostly disclosed, but they create ongoing influence over the local agent environment.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install clawdtalk-client - After installation, invoke the skill by name or use
/clawdtalk-client - Provide required inputs per the skill's parameter spec and get structured output
Version History
v2.0.5
-More bugfixes.
v2.0.3
Bug fixes.
v2.0.2
## clawdtalk-client 2.0.2
- Added `SETUP.md` with step-by-step configuration instructions for first-time users.
- Updated SKILL.md to direct new users to `SETUP.md` for complete setup guidance.
v2.0.1
**v2.0.1 Changelog**
- Added security, privacy, and endpoint usage info to documentation.
- `SKILL.md` now details required environment/config files and gateway integration steps.
- Improved transparency about data sent to external services.
- Minor updates to scripts and documentation for better setup clarity.
v2.0.0
Version 2.0.0 — Major upgrade adding AI Missions and server-driven automation support.
- Introduced support for AI Missions: design, track, and automate multi-step outreach campaigns with full state management.
- Added scripts/telnyx_api.py, a Python CLI for managing missions, state, and events with the backend server.
- Added critical workflow requirements: consistent slugs, manual mission lifecycle management, and mandatory state/event persistence.
- Included new sample config and templates for bug reports, features, and questions.
- Expanded skill dependencies to include Python 3.
- Updated documentation with critical operational guidance, architecture overview, and advanced usage patterns.
v1.3.0
- Adds comprehensive setup and usage instructions for voice calls and SMS messaging via ClawdTalk, powered by Telnyx.
- Details all client-side scripts for starting/stopping call connections, making outbound calls, and handling SMS.
- Documents configuration options in `skill-config.json` and provides troubleshooting tips.
- Metadata now specifies required binaries: bash, node, jq.
- Clarifies privacy handling for external calls and requirements for paid accounts when calling outside numbers.
v1.2.5
Added better post-call handling (report back to gateway)
v1.2.4
Addded purpose for outbound calls.
v1.2.3
clawdtalk-client 1.2.3
- Added documentation for outbound calls to external numbers and privacy mode.
v1.2.2
- Added outbound call functionality with the new scripts/call.sh script.
- Introduced usage documentation for call.sh, including status and end options.
- Removed missions support and scripts/missions.sh.
- Updated documentation to reflect the new capabilities and removal of missions.
v1.2.1
Added correct version number to info.
v1.2.0
SMS Reply Support: Incoming SMS messages now route to your main agent session
• Agent generates response and automatically sends reply via ClawdTalk
• SMS replies truncated to fit SMS limits
v1.1.2
fix: prioritize config with valid gateway token
Previously ws-client would use the first config file found, even if
it had no gateway.auth.token. This caused 401 errors for users with
old ~/.clawdbot/clawdbot.json files from before the OpenClaw rebrand.
Now it checks all config paths and prefers one with a valid token.
Fixes: deep tool 'trouble reaching agent' for migrated users
v1.1.10
- Added sample configuration file: skill-config.json.sample for easier setup.
- Introduced .gitignore to exclude unnecessary or sensitive files from version control.
- Updated documentation to reflect new configuration options: owner_name, agent_name, and greeting.
- Improved explanation of the WebSocket client to clarify agent session capabilities.
- Added troubleshooting advice for slow responses and clarified debug instructions.
v1.0.0
Initial Release
Metadata
Frequently Asked Questions
What is ClawdTalk?
ClawdTalk — Voice calls, SMS, and AI Missions for Clawdbot. It is an AI Agent Skill for Claude Code / OpenClaw, with 5289 downloads so far.
How do I install ClawdTalk?
Run "/install clawdtalk-client" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is ClawdTalk free?
Yes, ClawdTalk is completely free (open-source). You can download, install and use it at no cost.
Which platforms does ClawdTalk support?
ClawdTalk is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created ClawdTalk?
It is built and maintained by dcasem (@dcasem); the current version is v2.0.5.
More Skills