openclaw-phone

# 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. Environment variable: `CALLMYCALL_API_KEY` (preferred)
2. OpenClaw user config: `~/.openclaw/openclaw.json` under `skills.openclaw-phone.apiKey`
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. 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:

```
Authorization: Bearer YOUR_API_KEY
```

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
  - `id` (call SID)
  - `phone_number`
  - `task`
  - `started_at`
  - `status` (optional, updated when you fetch)

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

# Phone OpenClaw Skill

Focused OpenClaw skill for operating the CallMyCall API from chat.

Docs and portal:

- https://api.callmycall.com

## Install (local)

1. Clone or copy this repo into your OpenClaw skills folder.
2. Restart OpenClaw (or refresh skills) so it detects the new skill.

Common locations:

- `<workspace>/skills/openclaw-phone`
- `~/.openclaw/skills/openclaw-phone`

## Usage

Examples:

- "Call +46700000000 and confirm my appointment for Tuesday."
- "Show my recent calls."
- "End call 1."
- "Show results for call 2."
- "Prepare this call for 3pm and remind me to run it then."

## Files

- `SKILL.md` — primary instructions and workflows
- `references/api.md` — API reference subset
- `examples/prompts.md` — example prompts and expected actions

## API Key

Key lookup order:

1. `CALLMYCALL_API_KEY` environment variable
2. `~/.openclaw/openclaw.json` at `skills.openclaw-phone.apiKey`
3. One-time user prompt for current task only

This skill does not write config files automatically. If you want persistence, add the key manually to `~/.openclaw/openclaw.json`.

The skill must not store API keys in skill source files or memory/state files.

## Notes

This skill is pull based. It does not rely on webhook callbacks; results are fetched on demand.
It also does not create OS scheduler jobs (`cron`/launchd/task scheduler) or autonomous background runs.

See also:

- `docs/auth-config.md` - credential handling details
- `docs/event-updates.md` - options for event-like updates with a pull API