← Back to Skills Marketplace
Openclaw phone
by
Benjamin Waye
· GitHub ↗
· v1.0.1
· MIT-0
479
Downloads
1
Stars
0
Active Installs
2
Versions
Install in OpenClaw
/install openclaw-phone
Description
Use CallMyCall API to start, end, and check AI phone calls, and return results in chat. Use when the user asks to call someone, plan a future call, end a cal...
Usage Guidance
Before installing: (1) confirm the platform/registry metadata is updated to declare CALLMYCALL_API_KEY — the skill expects that key even though the top-level registry entry did not list it; (2) verify the correct CallMyCall base URL for your account (the docs mention both api.callmycall.com and a fly.dev backend — prefer the official domain or confirm the fly.dev host is legitimate for the provider); (3) avoid storing long-lived API keys in the skill — follow the SKILL.md advice to use an env var or one-time interactive key and only persist manually if you understand the risk; (4) be cautious about sending sensitive personal data (the API supports fields like personal_security_number in a persona object) — do not include PII unless absolutely necessary and authorized; (5) ask the skill author/owner (or registry operator) to fix the registry metadata mismatch so the platform can surface the credential requirement correctly. These issues suggest sloppy/unfinished packaging rather than explicit malice, but you should validate ownership and endpoints before granting credentials.
Capability Analysis
Type: OpenClaw Skill
Name: openclaw-phone
Version: 1.0.1
The openclaw-phone skill provides a well-structured interface for the CallMyCall AI telephony API, incorporating significant safety guardrails and security best practices. It implements a five-layer 'gating flow' that includes mandatory human confirmation before placing calls, blocks emergency/premium numbers, and strictly forbids the creation of persistent OS schedulers or autonomous background execution. Credential handling follows OpenClaw best practices, explicitly prohibiting the storage of API keys in state files or logs (SKILL.md, docs/auth-config.md).
Capability Assessment
Purpose & Capability
The SKILL.md and accompanying files clearly require a CALLMYCALL_API_KEY and explain how it's used; however the registry metadata at the top of the report lists no primary credential and 'Required env vars: none'. That mismatch is an incoherence — the skill will need an API key but the registry entry doesn't declare it, which can lead to missing prompts/validation in the platform. Other than that, the actions described (start/end/list calls, verify caller IDs, fetch recordings/transcripts) are coherent with a CallMyCall phone skill.
Instruction Scope
SKILL.md stays narrowly scoped to the call-management purpose: gathering phone, language, brief; doing validation; calling the CallMyCall API; storing a small recent_calls state. It explicitly forbids creating OS schedulers, storing API keys in skill files/state, and autonomous background runs. Two items worth noting: (1) the docs recommend using a specific backend base URL (https://call-my-call-backend.fly.dev) in addition to api.callmycall.com — using a non-official domain should be validated; and (2) the API accepts highly sensitive fields (e.g., personal_security_number inside a persona object) — the instructions do not forbid including PII in requests, so agents could transmit sensitive user data if prompted to do so.
Install Mechanism
This is an instruction-only skill with no install spec and no code files to execute at install time, so there is no downloader/extractor or package install risk.
Credentials
The skill legitimately needs a single service credential (CALLMYCALL_API_KEY) but the registry metadata does not declare it (incoherent). The SKILL.md correctly describes a limited key resolution order (env var, user config, prompt) and forbids persisting keys automatically, which is good. However the API surface allows sending PII and webhook URLs; ensure any API use is deliberate and avoid entering persistent credentials unless you trust the service and skill owner. The recommendation to prefer a fly.dev backend (different from the public api.callmycall.com hostname) raises an extra review step: confirm the correct base URL for your account.
Persistence & Privilege
The skill does not request always:true, does not ask to modify other skills, and explicitly tells agents not to create background schedulers or persist credentials automatically. It stores minimal per-skill state (recent_calls) which is appropriate for the described functionality.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install openclaw-phone - After installation, invoke the skill by name or use
/openclaw-phone - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
**Changelog for openclaw-phone 1.0.1**
- Clarified API key handling, emphasizing session-limited use and prohibiting automatic user config writes.
- Added explicit section for `from_number` validation, requiring preflight verification with relevant endpoints.
- Updated scheduling workflow to prohibit creating system schedulers (cron, launchd, etc) or background turns; skill may only prepare call plans for in-session execution.
- Modified call results flow to treat transcripts and recordings as sensitive—display excerpts only upon explicit request, and warn about the sensitivity of recording URLs.
- Added new metadata fields to SKILL.md (`primary_credential`, `required_env_vars`, `stores_credentials_in_user_config`, `requires_system_scheduler`).
- Added `agents/openai.yaml` (details not included).
v1.0.0
openclaw-phone 1.0.0
- Initial release of the openclaw-phone skill.
- Enables starting, ending, scheduling, and checking AI-powered phone calls via the CallMyCall API from chat.
- Implements strict API key handling and layered data collection ("layered gating") for secure and complete call setup.
- Maintains a recent calls list in state for easy retrieval and management.
- Supports OpenClaw-side scheduling (using cron) for future-dated calls.
- Allows users to review and confirm call details before placement and fetch call status, results, transcript, and recordings as needed.
Metadata
Frequently Asked Questions
What is Openclaw phone?
Use CallMyCall API to start, end, and check AI phone calls, and return results in chat. Use when the user asks to call someone, plan a future call, end a cal... It is an AI Agent Skill for Claude Code / OpenClaw, with 479 downloads so far.
How do I install Openclaw phone?
Run "/install openclaw-phone" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Openclaw phone free?
Yes, Openclaw phone is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Openclaw phone support?
Openclaw phone is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Openclaw phone?
It is built and maintained by Benjamin Waye (@benjaminwaye); the current version is v1.0.1.
More Skills