How to use the Add Another Dial Number agent skill

What is an agent skill and what does this one do?

An agent skill is a folder of instructions and optional scripts that an AI agent can load to perform a specific task. This skill, add-dial-number, covers one job: adding another phone number to a Dial channel that is already installed.

Each added number becomes its own public, threaded line. It gets its own messaging group, with each remote correspondent appearing as a thread inside it. The agent replies from whichever number a person texted, and existing lines are not changed.

What you need before you start

The skill stops unless the Dial channel is already installed. Run /add-dial first if it is not. The source lists these requirements: a NanoClaw install with the Dial channel installed, the Dial CLI on the PATH, a signed-in Dial account that owns the number, Node.js and jq for the check and capture commands, and a running NanoClaw host service, since ncl connects over a Unix socket.

If you need a new number, the account must have funds, because buying a number spends them.

• NanoClaw install with the Dial channel (/add-dial)
• Dial CLI on the PATH
• Signed in to a Dial account that owns the number
• Node.js and jq available
• A running NanoClaw host service
• Dial account funds if you must purchase a new number

How to install the skill

Download the ZIP from the skill page on this directory and unzip it into one of two locations. For a personal install, use ~/.claude/skills/. For a single project, use the .claude/skills/ folder inside that project.

Alternatively, if you use the Claude apps, open Settings, then Capabilities, then Skills, and upload the ZIP there.

• Personal: ~/.claude/skills/
• Per project: .claude/skills/ inside the project folder
• Claude apps: Settings → Capabilities → Skills, then upload the ZIP

How to trigger the skill with a request

You do not need a special command to use the skill. Ask the agent in plain language, for example that you want to add another Dial number, or that you want a support line added alongside your personal line. The skill's description says to use it when Dial is already installed and the operator wants an additional number.

The skill then walks the agent through the steps: checking that Dial is set up, listing your account's numbers, asking you to choose one, asking which agent group should answer it, and asking whether the line is strict or public.

Walk through the setup steps

The agent first confirms Dial is installed and that the multi-number adapter is present. If the adapter check fails, the skill says to run /update-skills, rebuild, and retry.

Next, it lists the numbers on your Dial account. If you need a new one, you purchase it yourself with the Dial CLI before entering it. The agent checks that the number you choose belongs to the signed-in account.

You then pick the agent group that will answer the number, give the line a display name, and choose inbound access. Strict admits only known users. Public lets anyone who knows the number reach the agent. The choice applies only to this number.

Finally, the skill creates the messaging group, wires it to the chosen agent group, restarts the service, and verifies that the pair exists.

• Confirm Dial and the multi-number adapter are installed
• Choose a Dial number on the account
• Select the agent group that answers it
• Name the line and set strict or public access
• Create the messaging group and wiring, then restart and verify

Example requests and outcomes

A typical request is a personal line plus a support line on one install. You would ask the agent to add your support number, then pick the agent group that handles support and choose strict or public access depending on who should be able to text it.

After the run, texts to the new number reach the selected agent as a separate thread, and replies go out from that number.

• Add a support number for an agent group that handles customer questions
• Add a second personal line that only known contacts can text (strict)
• Add a third line for a separate project, with its own agent group

Safety notes: scripts and network access

This skill runs scripts and uses the network. It calls the Dial CLI to list numbers and, if you choose to buy one, to purchase it, which may charge the Dial account. Treat the public setting with care: if inbound access is public, anyone who knows the number can reach the agent, which can trigger costs or misuse.

Before choosing public, decide whether the line really needs to be open to strangers. Strict is the safer default for lines meant only for known people.

• Purchasing a number spends account funds
• Public access lets anyone who knows the number reach the agent
• Existing lines are not changed by adding a new one

Troubleshooting common problems

If the multi-number check fails, run /update-skills, rebuild, and retry. If the number is rejected, sign in to the correct Dial account or purchase the number first, then enter its exact E.164 value, such as +14155550123.

If new texts land in an old line or replies use the wrong number, the running service may still have the old adapter, so refresh it and restart. If new inbound events never arrive, confirm that dial doctor --json reports listen.running as true and that dial local-target list --json includes NanoClaw's command target.

If ncl returns errors, the host service is probably not running, since ncl connects over a Unix socket.

• Multi-number check fails: run /update-skills, rebuild, retry
• Number rejected: check the account, or purchase first
• Wrong line or number: refresh the adapter and restart
• No inbound events: check dial doctor --json and dial local-target list --json
• ncl errors: confirm the host service is running