ClawHub

Ringg Voice Agent

v1.0.0

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.

⭐ 2· 1.3k·0 current·0 all-time
by@siddharthpilani
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
ℹ
Purpose & Capability
The name/description and SKILL.md consistently describe a Ringg AI voice integration (outbound calls, campaigns, assistants, webhooks). The requested actions (API calls to api.ringg.ai, webhooks, call management) are coherent with that purpose. However, the registry metadata claims 'Required env vars: none' and 'Primary credential: none' while the SKILL.md explicitly requires RINGG_API_KEY, RINGG_WORKSPACE_ID and optional assistant/number environment variables — this provenance/metadata mismatch is unexpected.
ℹ
Instruction Scope
SKILL.md gives concrete curl examples, webhook setup steps (including recommending running ngrok to expose a local endpoint), and configuration changes to openclaw.json. All instructions stay within the stated purpose (calling Ringg APIs and receiving webhooks). The ngrok webhook guidance is normal for dev but increases exposure risk for inbound call events and transcripts if used carelessly.
✓
Install Mechanism
Instruction-only skill with no install spec or code files to write to disk. This lowers risk because nothing is downloaded or executed by an installer.
!
Credentials
The runtime instructions require sensitive credentials (RINGG_API_KEY and RINGG_WORKSPACE_ID and optional assistant/from-number). Those are proportionate to the integration itself, but the skill's published metadata failing to declare them (and not naming a primary credential) is a problem: it can mislead administrators about what secrets will be needed or accessed. The skill also suggests placing API keys in openclaw.json which may increase exposure if that file is not securely stored.
✓
Persistence & Privilege
The skill does not request always:true and does not modify other skills or system-wide settings. It is user-invocable and allowed to be invoked autonomously (platform default).
What to consider before installing
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.

Like a lobster shell, security has layers — review code before you run it.

latestvk97bx7x0j4k0x4pw0jptwxevv580nyqv

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments