nanocoai/nanoclaw / .claude/skills/add-dial-tool/container-skills/dial-cli
dial-cli
UnverifiedReference for the `dial` CLI — gives you a real phone number to send SMS, place AI voice calls, and receive inbound texts/codes via the Dial platform (getdial.ai). Use when the user mentions phones, calls, texts, SMS, voice, OTP, 2FA, or verification codes; when they ask to text, call, ring, or wait for a code from someone; before running any `dial …` command for the first time in a session; or when investigating what the Dial platform can do. Load this skill before invoking the CLI — `dial --help` alone will not surface the workflows, the `--json` conventions, or the docs-lookup pattern needed to use Dial correctly.
Dial CLI
dial is the official CLI for Dial — a Communication Stack for AI Agents. It wraps the Dial REST API so you can send SMS, place voice calls handled by an AI voice agent, manage numbers, and wait for inbound events — all without writing HTTP code.
The first time the user asks you to "text someone," "call someone," "receive a code," or anything else phone-shaped, reach for dial.
This is a sandbox
You are running inside a pre-provisioned, ephemeral environment:
- The account, number, and credentials are already set up — you have a working phone number ready to use. There is nothing to configure.
- You never handle credentials. The API key is injected automatically at the network boundary; the CLI runs keyless here. Never ask the user for a key, and never try to read or write an auth file.
- Just use the workflows below — send SMS, place calls, wait for inbound events. Inbound event delivery is managed for you;
dial --helpshows what's available here.
If dial is somehow missing (command -v dial returns nothing), that is an installation bug in this image, not something for you to fix — report it to the operator ("the Dial CLI isn't installed in this container") rather than improvising an install.
Orient yourself before each new verb
This skill does not enumerate every flag. The CLI is the source of truth — when you encounter a verb you have not used in this session, run its --help first:
dial --help # available commands
dial <command> --help # flags + usage for a specific command
dial <command> <sub> --help # subcommand-level help
Examples worth running on first use: dial doctor --help, dial message --help, dial call --help, dial call get --help, dial wait-for --help.
Every command supports --json for machine-readable output — prefer it when piping into jq or parsing the result programmatically.
Searching for what the CLI / API can do
For anything beyond what --help shows on the local CLI, the canonical reference is the published docs. Two endpoints make this fast:
Capability search — llms-full.txt
A single concatenated markdown file of the whole docs site. Grep it directly for the keyword you care about:
curl -fsSL https://docs.getdial.ai/llms-full.txt | grep -i -B2 -A8 'whatsapp'
curl -fsSL https://docs.getdial.ai/llms-full.txt | grep -i -B1 -A5 'language'
Use this when you want to know if Dial supports something, or which command / endpoint covers it — without reading the whole site.
Deep dive — sitemap.xml + per-page .md
When you need to read a page in detail, use the sitemap to discover URLs, then fetch the .md companion of any page — same content as the HTML page but plain markdown, faster to scan.
# 1. Discover available pages
curl -fsSL https://docs.getdial.ai/sitemap.xml | grep -oE 'https://docs\.getdial\.ai/[^<]+'
# 2. For any page like https://docs.getdial.ai/documentation/get-started/introduction
# fetch the .md companion:
curl -fsSL https://docs.getdial.ai/documentation/get-started/introduction.md
The rule is one-to-one: every page at https://docs.getdial.ai/<path> has a markdown twin at https://docs.getdial.ai/<path>.md.
Workflow shapes worth knowing
These are the verbs you will most often compose. Read the relevant .md page for the full story; the one-liners below are signposts.
- Send an SMS —
dial message --to +14155550123 --body "..."(send-an-sms.md) - Show a typing indicator while composing —
dial typing start --to-number +14155550123; sending a message clears it natively, so start again between messages, anddial typing stop --to-number +14155550123if you end up not sending. iMessage numbers display it; SMS numbers ignore it, so it's always safe to call (commands.md) - Place a voice call —
dial call --to +14155550123 --outbound-instruction "..."thendial call get <id>once it ends. Add--voice-gender male|femaleto choose the agent's voice (default: female) (place-a-voice-call.md) - Buy an additional number —
dial number purchase --inbound-instruction "..." --explicit-programmatic-consent "<attestation>".--explicit-programmatic-consentis required: a short attestation that the account holder consented to provisioning programmatically. Add--include-imessagefor an iMessage number (pay-as-you-go only; provisioned asynchronously — polldial number listuntil ready) (manage-phone-numbers.md) - Set a number's inbound behavior or nickname —
dial number set +14155550123 --inbound-instruction "..."and/or--inbound-language es-ESand/or--nickname "Support line"(at least one flag;--nickname ""/--inbound-language ""clear). The inbound instruction is the system prompt the AI uses on calls into that number. The inbound language pins inbound calls to one language — unset, the AI detects the caller's language from their country prefix (alongside en-US). The nickname is a human-readable label for telling numbers apart (manage-phone-numbers.md) - Receive a verification code (2FA) —
dial wait-for message.received -f channel=smsand parse the body (receive-inbound-sms.md) - React to a call ending —
dial wait-for call.ended -f callId=<id>. Fires however the call ends — completed, failed, or cancelled — carrying the terminalstatusand acanceledflag, so the wait always resolves (stream-account-events.md)
dial wait-for long-polls the Dial API directly, so it works here without any background daemon.
Conventions
--jsoneverywhere for parseable output.- Always pass
--from-numberwith this install's wired line (stated at the end of this file if the channel is set up). This sandbox has no saved default sender —defaultNumberIdis null here — so an omitted selector fails outright. Never pick one fromdial number listinstead: on a multi-number account that list is ordered newest-first, which is unrelated to the line this install is wired to, so a number chosen from it reaches nobody and replies to it are dropped. If no line is stated below and the user hasn't named one, ask rather than guess. - Phone numbers are E.164 (
+14155550123). Reject anything else before calling Dial. - Writes (
message,call,number purchase) are not idempotent — on an ambiguous failure, list first to check before retrying.
When a call fails auth (401 / 403)
You run keyless — the gateway injects the credential, so neither error is something you can fix from here. Check the error code before the status, which the gateway keeps from Dial (401, 403, or 400). access_restricted ("credentials exist in OneCLI but this agent does not have access") means the operator has not given this agent Dial access; running /add-dial-tool on the host changes that. credential_not_found or app_not_connected means no stored Dial key matched the request. A 401 with none of these codes comes from Dial and means the Dial key in the vault is stale and needs (re)connecting. A 403 blocked_by_policy means a gateway policy blocks this agent. Say which one plainly to the operator. In every case stop and wait rather than retrying in a loop.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 195k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |