CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dial-cli

Reference 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.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, executable reference — nearly every line is a runnable command or a Dial-specific gotcha (keyless auth injection, defaultNumberId null, newest-first ordering trap, non-idempotent writes), with explicit validation and recovery loops for every risky path. Only mild trimming opportunities exist in the sandbox section and the intro paragraph.

Suggestions

Tighten the sandbox section by merging the reassurance bullets ("There is nothing to configure" / "Just use the workflows below") into the credential-handling bullet.

Drop the intro paragraph restating trigger phrases ("The first time the user asks you to 'text someone'...") — the frontmatter description already carries that job.

DimensionReasoningScore

Conciseness

Largely efficient — the curl snippets and one-liner commands carry no padding, and almost all prose is Dial-specific (keyless auth, newest-first ordering trap, non-idempotent writes) rather than concepts Claude already knows — but the sandbox reassurance bullets ("There is nothing to configure", "Just use the workflows below") and the intro's restatement of the frontmatter triggers ("The first time the user asks you to 'text someone'...") could be trimmed. Not 5 (some over-explanation remains), not 3 (unnecessary explanation is minor, not pervasive).

4 / 5

Actionability

Fully executable, copy-paste-ready commands cover the common cases — `dial message --to +14155550123 --body "..."`, `dial number purchase --inbound-instruction "..." --explicit-programmatic-consent "<attestation>"`, `dial wait-for message.received -f channel=sms` — plus edge-case specifics ("--nickname `""` / --inbound-language `""` clear", "poll `dial number list` until ready"). Not 4 — there are no gaps in executable coverage; the few placeholders hold inherently user-supplied content (prompt text, attestation).

5 / 5

Workflow Clarity

Explicit validation and feedback loops are present throughout: "poll `dial number list` until ready" (async provisioning), "on an ambiguous failure, list first to check before retrying" (non-idempotent writes), "In every case stop and wait rather than retrying in a loop" (auth failures), and pre-flight validation ("Phone numbers are E.164 ... Reject anything else before calling Dial"). Multi-step sequences like place-call → "`dial call get <id>` once it ends" are clear. Not 4 — checkpoints are explicit and include recovery guidance, not merely present.

5 / 5

Progressive Disclosure

A clear overview with one-level-deep, well-signaled references: each workflow bullet links its exact docs page (send-an-sms.md, place-a-voice-call.md, manage-phone-numbers.md, receive-inbound-sms.md, stream-account-events.md), and the docs-search section teaches self-serve lookup rather than inlining detail; no bundle files exist, so nothing is nested. Not 4 — there are no organization gaps; sections are navigable and content is appropriately split between inline signposts and the published docs.

5 / 5

Total

19

/

20

Passed

Description

90%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An excellent description: explicit what/when with rich, natural trigger terms and a clearly distinct niche. The only deductions are the second-person voice ("gives you"), which costs a specificity point per the rubric's voice rule, and omission of the number-management capability from the action list.

Suggestions

Rewrite in third person (e.g., "Gives the agent a real phone number to send SMS...") — the second-person "gives you" triggers the rubric's voice penalty.

Mention number management (e.g., "purchase additional numbers and set inbound behavior/nicknames") alongside send/call/receive to close the coverage gap.

Tighten the final sentence ("Load this skill before invoking the CLI — `dial --help` alone will not surface...") to a single clause; its detail largely restates the trigger guidance already given.

DimensionReasoningScore

Specificity

"send SMS, place AI voice calls, and receive inbound texts/codes" lists three concrete actions, but number management (purchase/set) is absent — matching anchor 4 ("several specific actions; minor gaps") — and the second-person "gives you a real phone number" incurs the rubric's -1 voice penalty, landing at 3. Not 5 (coverage is not comprehensive) and not 2 (actions are concrete, not generic).

3 / 5

Completeness

Explicitly answers both: what ("gives you a real phone number to send SMS, place AI voice calls, and receive inbound texts/codes via the Dial platform") and when ("Use when the user mentions phones, calls, texts, SMS, voice, OTP, 2FA, or verification codes... before running any `dial ...` command for the first time") with concrete trigger phrases. Not 4 — the 'when' clause is fully explicit and multi-triggered, not merely adequate.

5 / 5

Trigger Term Quality

"phones, calls, texts, SMS, voice, OTP, 2FA, or verification codes" plus natural verb phrases "text, call, ring, or wait for a code from someone" give comprehensive synonym coverage of what a user would naturally say. Not 4 — no common natural term is missing.

5 / 5

Distinctiveness Conflict Risk

"Reference for the `dial` CLI ... via the Dial platform (getdial.ai)" carves a clear phone-communication niche with distinct triggers (phones, SMS, OTP, 2FA, ring), so conflict risk with other skills is minimal. Not 4 — there is no meaningful overlap with a neighboring skill.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

nanocoai/nanoclaw

Path

.claude/skills/add-dial-tool/container-skills/dial-cli/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.