Amber — Give Your Agent Real Phone Capabilities

v5.5.8

Give your OpenClaw agent real phone capabilities: inbound answering, outbound calls, booking, screening, CRM memory, and real-world phone task execution.

⭐ 5· 1.7k·2 current·2 all-time

byAbe Batthish@batthis

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for batthis/amber-phone-capabilities.

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "Amber — Give Your Agent Real Phone Capabilities" (batthis/amber-phone-capabilities) from ClawHub.
Skill page: https://clawhub.ai/batthis/amber-phone-capabilities
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: TWILIO_ACCOUNT_SID, TWILIO_AUTH_TOKEN, TWILIO_CALLER_ID, OPENAI_API_KEY, OPENAI_PROJECT_ID, OPENAI_WEBHOOK_SECRET, PUBLIC_BASE_URL
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Canonical install target

openclaw skills install batthis/amber-phone-capabilities

ClawHub CLI

Package manager switcher

npx clawhub@latest install amber-phone-capabilities

Security Scan

Capability signals

CryptoCan make purchasesRequires OAuth tokenRequires sensitive credentials

These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.

VirusTotal

Benign

View report →

OpenClaw

Benign

medium confidence

✓

Purpose & Capability

The name/description (phone-capable agent) align with the requested env vars (Twilio credentials, OpenAI keys), required binaries (node, ical-query), and included runtime code (Twilio/Telnyx providers, OpenAI Realtime bridge, CRM, calendar). The set of requested credentials is what you'd expect for a telephony+LLM bridge.

ℹ

Instruction Scope

The SKILL.md and AGENT.md tightly specify runtime behavior (what tools can be called, calendar argument validation, SUMMARY_JSON token usage, not exposing internal prompts). This is good. However there are small contradictions in the docs around confirmation enforcement (some sections claim router-level programmatic enforcement, another note says confirmation is in the LLM layer). That ambiguity matters for safety-critical actions (sending messages, destructive ops) — you should verify the actual router implementation enforces confirmations programmatically. Also AGENT.md contains broad behavioral instructions for the voice persona (including sexualized persona choices) — not a security bug, but an operational/policy consideration for some deployments.

✓

Install Mechanism

Install uses a normal Node/npm workflow (cd runtime && npm install && npm run build). All code is included in the package; there are no downloads from obscure URLs or archive extraction steps in the install spec. There are native build dependencies (better-sqlite3) documented and requiring platform toolchains; the install spec does not silently execute system-level installers or download untrusted binaries.

ℹ

Credentials

Required env vars (TWILIO_ACCOUNT_SID, TWILIO_AUTH_TOKEN, TWILIO_CALLER_ID, OPENAI_API_KEY, OPENAI_PROJECT_ID, OPENAI_WEBHOOK_SECRET, PUBLIC_BASE_URL) are relevant to a Twilio + OpenAI realtime bridge. The number of secrets is appropriate for the service being integrated, but these are high-sensitivity credentials (telephony billing and a live OpenAI key). The package also documents optional gateway tokens and CRM DB path. Ensure you use dedicated service keys with least privilege and monitoring.

✓

Persistence & Privilege

always:false (not force-included) and model invocation enabled (default) — expected for a skill that must act during calls. The project includes helper scripts (dist-watcher, LaunchAgent examples) that, if you run them, will persist a watcher/restart mechanism on the host; these are optional user actions but increase persistence if installed. The skill does not request or appear to modify other skills' credentials or config paths.

Assessment

Plain-language checklist before installing: - Verify the source: the SKILL.md points to a GitHub repo; confirm you trust that repository and the exact commit you install. Registry metadata owner ID is not human-friendly — prefer installing directly from the upstream repo you inspected. - Credentials: this requires Twilio account credentials and an OpenAI API key (and webhook secret). These give the runtime control over phone calls and access to OpenAI. Use dedicated, least-privilege keys and monitor usage/billing. Consider setting usage limits on the OpenAI key. - Data flow: audio and transcripts are processed via OpenAI Realtime (cloud). While CRM DB is local by design, call audio/transcripts leave your machine by necessity. If privacy is a concern, review which data is forwarded and consider on-prem alternatives (the docs include an Asterisk roadmap). - Confirmation enforcement: docs contain contradictory statements about whether confirmations for side-effecting actions are enforced at router code or left to the LLM. Before enabling outbound messages or payment-related flows in production, verify the compiled runtime enforces confirmation server-side (test destructive actions and confirm a missing confirmed flag is rejected). - Review handler code for third-party skills: Amber supports loading handler.js from amber-skills; the manifest allowlist is present but review amber-skills/*/handler.js files you plan to enable. The system offers a policy layer, but manual review reduces risk. - Native dependencies & build: CRM uses better-sqlite3 which requires native toolchains. Ensure build tools are available (build-essential/python3 on Linux, Xcode license on macOS) or expect install failures. - Startup/auto-restart scripts: the repo includes a dist-watcher and LaunchAgent examples that, if you run them, will persist a background process. Only enable these if you accept that behavior and have inspected the plist/scripts. - Test in a sandbox: run on an isolated host or test account to verify behavior (call flows, confirmation enforcement, where SUMMARY_JSON ends up) before routing real customer traffic or production numbers. If you want, I can highlight specific lines/files to inspect (router/index.ts, runtime/src/skills/loader.ts, runtime/src/skills/router.ts, runtime/src/providers/twilio.ts, and amber-skills/*/handler.js) and summarize what to look for in each.

✗

dashboard/scripts/serve.js:70