OpenClaw Phone Receipt

Trigger and manage OpenClaw outbound phone receipts via ElevenLabs+Twilio for task completion/failure notifications. Use when user asks to call them after finishing/failing a task, asks to enable/disable fixed command toggles ("phone-receipt=on/off"), asks to test call quality, or asks to persist phone receipt behavior across sessions.

This skill does what it claims (initiate outbound phone calls via ElevenLabs/Twilio) but the package metadata did not list the sensitive environment variables the scripts actually use. Before installing or supplying keys: (1) verify you trust the developer/source, (2) ensure you only provide an ElevenLabs API key with minimal required scopes (ConvAI read) and use a throwaway/test phone number when testing, (3) store .env files securely (avoid committing them), (4) understand that Twilio/ElevenLabs calls may incur cost and may require verified numbers, and (5) prefer adding the required env vars to the manifest or ask the publisher why the registry metadata omits them. If you cannot confirm these points, treat this skill with caution and avoid providing production credentials.

Type: OpenClaw Skill Name: openclaw-phone-receipt Version: 1.0.1 The OpenClaw Phone Receipt skill is designed to manage outbound phone notifications via ElevenLabs and Twilio. The `SKILL.md` provides clear instructions for the agent to manage state and execute local scripts. The `scripts/trigger_call.sh` script makes authenticated API calls to `https://api.elevenlabs.io` using API keys and phone numbers loaded from environment variables or a local `.env` file, which is necessary for its stated purpose. The `scripts/set_phone_receipt_state.py` manages local state in a JSON file. All actions are transparently aligned with the skill's description, and there is no evidence of data exfiltration to unauthorized endpoints, malicious execution, persistence, or prompt injection attempts against the agent for harmful objectives.