clawdtalk-client

What This Skill Does

The clawdtalk-client skill provides Clawdbot with full-duplex voice communication, SMS messaging capabilities, and autonomous mission management. By acting as a bridge between the local OpenClaw agent and the Telnyx-powered ClawdTalk infrastructure, it enables your bot to perform real-world outreach. Whether you are running complex multi-step lead generation campaigns, managing automated scheduling, or providing voice-based customer support, this skill handles the heavy lifting of state synchronization and communication protocols.

Installation

To install the skill, run the following command in your Clawhub terminal:

clawhub install openclaw/skills/skills/dcasem/clawdtalk-client

Before launching, ensure you have read the SETUP.md file in the skill directory to configure your API keys and environment variables properly. It is highly recommended to store your API key using the CLAWDTALK_API_KEY environment variable rather than placing it in skill-config.json to maintain security. Once installed, confirm your connection by running python scripts/telnyx_api.py list-state to ensure the communication pathways are established.

Use Cases

1. Automated Sales Outreach: Use the agent to call prospects, leave personalized voicemails, and follow up with SMS messages based on their initial feedback.
2. Voice-Activated Support: Allow users to call your bot's assigned phone number to get real-time assistance, with transcripts sent directly to the agent for processing.
3. Event Coordination: Use autonomous missions to ping lists of contacts via SMS to confirm appointments and update the mission state dynamically based on their replies.

Example Prompts

1. "ClawdTalk, initialize a new mission titled 'Q4 Outreach Campaign' and load the contact list from my local directory to start the first round of SMS messages."
2. "Check the current status of the 'window-washing-contractors' mission and verify if the latest calls to the provided lead list were successful."
3. "Send an update to the dashboard: mark the 'initial-contact' step as completed for the current mission and trigger a follow-up call in 30 minutes."

Tips & Limitations

• Slug Consistency: The most critical aspect of this skill is slug management. The slug generated during init must be preserved exactly across all commands. Mismatched slugs result in silent failures where the server is unaware of your progress.
• Mission Lifecycle Ownership: Remember that you own the mission status. The server will display 'Running' indefinitely unless you explicitly report progress (e.g., in_progress to completed) and eventually call the completion command.
• Data Privacy: All interactions involve external transmission to Telnyx. Only use this skill if you have verified that your data privacy requirements permit third-party processing of voice and text logs.
• Persistence: Always call 'save to memory' after any interaction to ensure the agent state is preserved across potential environment restarts.