What problem does it solve?
Giving sandboxed AI agents real phone capabilities (SMS, AI voice calls, verification codes) normally means baking credentials into images or environment variables, which leaks the key to every agent. This Skill installs the Dial CLI as a container tool and injects the API key per agent through OneCLI, so the operator chooses exactly which agents can text or call while all others are blocked at the gateway.
Core Features & Use Cases
- Container tool installation: Adds the pinned
@getdial/cli to the agent image manifest, mounts a sandbox-aware dial-cli skill, and rebuilds the image so agents get the CLI on PATH.
- Per-agent credential scoping: Registers the Dial API key in the OneCLI vault and creates per-agent block rules on api.getdial.ai, so unchosen agents receive
403 blocked_by_policy while chosen agents run keyless.
- Idempotent, re-runnable setup: Every step is safe to re-run, so re-running the skill changes which agents may use Dial without breaking existing configuration.
- Use Case: An operator wants the Sales agent to text leads and place follow-up calls, but not the Support agent. They run this skill, pick the Sales agent id, and only that agent can use Dial from inside its container.
Quick Start
Run the add-dial-tool skill from the NanoClaw repo on the host and choose which agent groups may use Dial when prompted.
