CallMyCall (OpenClaw Skill)

This skill helps you operate CallMyCall from chat. It is pull based (no webhook callbacks): you start a call, store the returned call ID in state, and later fetch status and results on demand.

API Key Resolution (OpenClaw best practice)

Resolve credentials in this order:

1. 1. Environment variable: CALLMYCALL_API_KEY (preferred)
2. OpenClaw user config: ~/.openclaw/openclaw.json under INLINECODE2
3. If still missing, ask for a one-time key for the current task only.
4. Only if the user explicitly asks for persistence, provide manual instructions for saving the key to ~/.openclaw/openclaw.json.

Persistence rules:

• - Never store API keys in SKILL.md, examples, references, or memory/state files.
• Do not write API keys into recent_calls or any conversation-visible output. Do not tell the user “I won’t echo it back.”
• Use interactive keys for the current task only.
• Do not write user config files automatically from this skill.

How This Skill Should Work

1. 1. Resolve API key using the order in "API Key Resolution (OpenClaw best practice)".
2. Collect required call info using a layered gating flow (below).
3. Present a short review summary and ask for confirmation.
4. On confirmation, call POST /v1/start-call.
5. Store the returned sid in state as a recent call.

Required Auth

Send the API key in the Authorization header:

CODEBLOCK0

Never echo the API key back to the user or include it in logs/summaries.

Stateful Calls List (required)

Maintain a list (last 10) of recent calls in state:

• - recent_calls: array of objects

Use this list to let the user say "end call 1" or "show results for call 2".

Layered Gating Flow (copy from web app)

Do not rely on a single validation step. Use all layers below.

Layer 1: Structured collection contract

Do not finalize a task until all required fields exist:

• - INLINECODE14
• INLINECODE15
• INLINECODE16 (background + goals)

Layer 2: Task gap analysis

When the user gives the initial request, analyze what is missing. Then ask only for missing info. If the user answers partially, repeat analysis and keep asking for the remaining gaps.

Layer 3: Prompt level enforcement

While missing info exists, continue gathering required fields. Do not proceed to the call until all required fields are present.

Layer 4: Runtime validation before finalizing

Before sending the call request:

• - Ensure phone exists and is E.164
• Block emergency or premium numbers
• Ensure from_number is not the same as INLINECODE18
• If from_number is requested, run caller-ID preflight:

• - Normalize language; normalize voice fields (genderVoice, openaiVoice) only if provided
• If scheduling is present, parse and clamp to a valid time

Layer 5: Human review gate

Present a short review summary:

• - Phone number
• Call brief (background + goals)
• Language (and voice if provided)
• Any schedule

Ask: "Confirm and place the call?" Do not proceed without explicit confirmation.

Workflows

Start a Call

1. 1. Collect required fields using the layered gating flow.
2. If from_number is provided, run caller-ID preflight via GET /v1/verified-caller-ids.
3. If requested from_number is not verified, ask user to choose:

1. 4. If a schedule/time is requested, follow Scheduled Requests (No Cron) below instead of calling the API immediately.
2. Otherwise call POST /v1/start-call.
3. Store the returned sid in recent_calls.
4. Reply with confirmation and the call ID.

Scheduled Requests (No Cron)

Because the API has no scheduling field:

1. 1. Collect all required fields now.
2. Save a compact call plan in skill state only for in-session follow-up.
3. Do not create or modify OS schedulers (cron, launchd, task scheduler) and do not run autonomous background turns.
4. Offer one of these safe options:

If the user asks to schedule for later, explain that this skill does not create background jobs; it can prepare the call plan and execute when the user confirms in-session.

List Recent Calls

1. 1. Read recent_calls from state.
2. For each call, fetch status via GET /v1/calls/:callId if needed.
3. Display a numbered list.

Retry Until Answered (important)

When the user asks to call repeatedly until answered:

1. 1. Place one call with POST /v1/start-call.
2. Poll GET /v1/calls/:callId until terminal status.
3. Treat response as either flat (status, duration) or nested (call.status, call.duration).
4. If status is busy, no-answer, failed, or canceled, wait requested interval and place next call.
5. Stop retry loop when:

1. 6. Report each attempt (call ID + status) back to user.

Implementation note: keep one base URL per run (https://call-my-call-backend.fly.dev preferred) and use it consistently for both start + status endpoints.

End a Call

If the user says "end the call" without specifying which, list recent calls and ask which one.

If there is only one active call, confirm and end it.

Call:

• - POST /v1/end-call with { callSid }.

Get Results

When the user asks for call results:

1. 1. Fetch status via GET /v1/calls/:callId.
2. If available, fetch transcript via GET /v1/calls/:callId/transcripts/stream.
3. If the call was recorded, fetch recording URL via GET /v1/calls/:callSid/recording.

Return:

• - Status (completed, failed, canceled)
• Short summary (1 to 3 bullets)
• Transcript excerpt (first few lines, only after user asks to view transcript content)
• Recording URL (if present, warn that URL access may expose sensitive audio)

Safety and UX

• - If user input is ambiguous, ask a clarification question.
• Never expose secrets or store API keys in transcript.
• Treat transcripts and recordings as sensitive; share only minimal excerpts requested by the user.
• Never create persistent scheduler entries or autonomous background execution from this skill.
• If a request fails, show the HTTP error and suggest next steps.

References

• - Full API reference: INLINECODE57
• Examples: INLINECODE58