Ring-a-Ding
v0.1.1Use the rad CLI to place outbound AI phone calls. Requires a Ring-a-Ding API key and an OpenAI API key.
⭐ 0· 53·0 current·0 all-time
by@vlbeta
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill claims to use the 'rad' CLI to place AI phone calls and requires the 'rad' binary plus RAD_API_KEY and OPENAI_API_KEY. Those binaries and environment variables are consistent with a service that both needs a vendor API key (RAD_API_KEY) and optionally uses the user's OpenAI key for LLM calls.
Instruction Scope
SKILL.md only instructs the agent to run the 'rad' CLI commands (call, status, wait, end, etc.), pass JSON via stdin for complex options, and optionally store keys in ~/.config/ring-a-ding/config.json. It does not direct the agent to read unrelated system files, other credentials, or to transmit data to unexpected endpoints.
Install Mechanism
Installation is via an npm package (ring-a-ding-cli) that creates the 'rad' binary. Using npm is a common, traceable mechanism but does write executable code to disk and runs package install scripts; this is a moderate-risk install method compared with an instruction-only skill or well-known OS package manager, but it is proportionate to providing a CLI.
Credentials
Only RAD_API_KEY and OPENAI_API_KEY are required, with RAD_API_KEY designated primary. Both are justifiable: RAD_API_KEY to authenticate with the Ring-a-Ding service and OPENAI_API_KEY if the CLI delegates LLM calls to the user's OpenAI account. The number and type of env vars are proportionate to the described functionality.
Persistence & Privilege
The skill is not 'always' enabled and may be invoked by the user. It mentions storing keys in ~/.config/ring-a-ding/config.json, which is typical for a CLI and limited to the skill's own config; there is no request to modify other skills or system-wide settings.
Assessment
This skill appears coherent, but take these precautions before installing: 1) Verify the npm package source (ring-a-ding-cli) and inspect its npm page and repository to ensure it matches the vendor (https://ringading.ai). 2) Understand that installing an npm CLI will place executable code on disk—review maintainers, recent releases, and install scripts. 3) Be aware that the skill can store credentials in ~/.config/ring-a-ding/config.json; protect that file and rotate keys if needed. 4) If you prefer vendor-handled LLM calls, confirm whether the service requires your OPENAI_API_KEY or can operate without it; if required, consider using a dedicated/sandbox OpenAI key with limited usage/billing. 5) Avoid passing highly sensitive personal data in calls unless you have reviewed the vendor's privacy/security policy and are comfortable with how call content is processed and retained.Like a lobster shell, security has layers — review code before you run it.
latestvk978h6mn4zzx3jf4tavaxne1fs84rad7
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
Binsrad
EnvRAD_API_KEY, OPENAI_API_KEY
Primary envRAD_API_KEY
Install
Install Ring-a-Ding CLI (npm)
Bins: rad
npm i -g ring-a-ding-cli