Ringg Voice Agent

Integrate Ringg AI voice agents with OpenClaw for making, receiving, and managing phone calls powered by Ringg's Voice OS. Use this skill when the user wants to: (1) make outbound voice calls via Ringg AI agents, (2) trigger Ringg AI campaigns from OpenClaw, (3) check call status or retrieve call history/analytics from Ringg, (4) manage Ringg AI assistants (list, create, update), (5) connect OpenClaw to Ringg's voice platform for automated phone interactions like lead qualification, feedback collection, appointment reminders, or order confirmations, (6) set up Ringg AI as a voice provider for the OpenClaw agent. Triggers on mentions of "ringg", "voice call", "phone call via ringg", "ringg agent", "ringg campaign", "voice AI call", or any request to initiate/manage calls through the Ringg AI platform.

This skill appears to be a legitimate Ringg voice integration, but there are two red flags you should address before installing: (1) the registry metadata does NOT list the environment variables the SKILL.md requires (RINGG_API_KEY, RINGG_WORKSPACE_ID, etc.). Treat that as a metadata bug — confirm with the skill author/source which credentials are actually needed and how they will be stored. (2) Source/homepage is unknown. Prefer skills that link to an official repository or vendor page so you can verify authenticity. Operational notes: only provide a Ringg API key with the minimal permissions needed, avoid putting secrets in widely readable config files, protect any webhook endpoint (use HTTPS and a signing secret), and be cautious when using ngrok or exposing local endpoints because inbound calls and transcripts may contain sensitive PII. If you cannot verify the author or origin of this skill, consider requesting an official Ringg-provided skill or adding the integration manually with vetted code.

Type: OpenClaw Skill Name: ringg-voice-agent Version: 1.0.0 The skill integrates OpenClaw with Ringg AI for voice calls, using standard API interactions via `curl` commands to `https://api.ringg.ai`. It requires `RINGG_API_KEY` from environment variables, which is passed in `Authorization` headers, a common practice for API integrations. The `SKILL.md` provides clear, purpose-aligned instructions for the AI agent, without any evidence of prompt injection attempts to subvert the agent's behavior. While `ngrok` is mentioned for webhook setup, it is presented as a manual configuration step for the user/environment, not an action for the agent to execute as part of its skill functionality.