clawcall — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited clawcall (Agent Skill) and scored it 66/100 (yellow). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 8 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 8 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
ClawCall lets you make real US phone calls for the user. A voice AI agent dials, speaks, handles menus or hold time, and returns the transcript, outcome, and recording link when available. The first outbound call can auto-provision an API key.
Base URL: https://api.clawcall.dev
The phone agent only knows the Call instructions you send as task. More relevant detail is better. Build a complete briefing before calling, and do not make the user supply public/business facts you can reasonably look up yourself.
| User intent | Do this |
|---|---|
| Call someone now | Build rich Call instructions, POST /call, then poll GET /call/{call_id} until lifecycle = "finalized". |
| Get through to a person / connect me | Use outbound calling with bridge_number and a handoff trigger in the Call instructions. |
| Compare options across businesses | Run a small call campaign, optionally 3-4 parallel information-only calls with no commitments. |
| Set up my ClawCall profile/personality | Configure global voice/personality/greeting and, if needed, inbound answering profile. |
| Configure how my number answers calls | Use inbound profile setup. Do not POST /call. |
| What calls came in? | Poll inbound history with GET /me/calls?direction=inbound.... |
| Link this agent to my ClawCall account | Use the saved API key to produce the sign-in link. |
| API error, quota, plan, retry, balance | Handle exactly from returned code/action; preserve URLs verbatim. |
Educate at decision points, not as a generic pitch.
At the start of any conversation involving ClawCall, check ~/.config/clawcall/key.json or the host secret store. If an API key exists, send it as X-Api-Key. If a saved user phone number exists, reuse it as the default callback, reservation contact, live handoff bridge_number, or inbound handoff_number when appropriate.
The first unauthenticated POST /call response can include an api_key. Save it immediately. When you first collect the user's own phone number, save that too:
{
"api_key": "clawcall_sk_...",
"user_phone_number": "+15559876543"
}If the user provides a ClawCall API key, replace any saved key with it.
If the user gives their phone number for a reservation, callback, live handoff, or inbound handoff, persist it until they change or remove it. Do not treat the saved user phone number as account verification or ownership proof.
To connect this agent to the user's ClawCall account, load the saved API key and send:
https://clawcall.dev/sign-in?token=<api_key>Do not create a new key for account linking. If no saved key exists, explain that this agent needs to make its first ClawCall call before it has a key to link.
Use profile setup when the user asks how ClawCall should sound, introduce itself, or answer calls.
voice is the audio voice only: jessica (default), sarah, chris, or eric.personality is reusable style and behavior for outbound and inbound calls. Include assistant identity, tone, persistence, caution, and decision boundaries. Do not put one-call facts, dates, account numbers, or booking details here.greeting is the user's preferred outbound opener. Keep it short; do not rely on it for instructions, AI disclosure, or recording disclosure.instructions are the standing briefing for future unknown callers: who the assistant represents, what to collect, when to hand off, what never to promise or disclose, and what to report.For a good setup, ask only for the assistant name/role, desired tone, hard boundaries, and default handoff/callback number when useful. See profile and personality.
Before asking the user, make a real effort to fill in public or standard details yourself.
Find these yourself when lookup tools are available:
Ask the user mainly for private or decision-making details:
Do not ask "what is the restaurant's phone number?" if a normal lookup should find it. Look it up, pick the official or most reliable number, and ask only if there are multiple plausible locations, conflicting numbers, or low confidence.
If the business is likely closed before 8 AM, after 6 PM, or on a weekend local time, mention it and ask whether to try now or wait.
For complex calls, do call reconnaissance before dialing. Use public research and common sense to anticipate the call shape:
Do moderate probing. Ask for the few facts that prevent a useless or risky call, then call. Do not front-load every possible question.
For OTPs, payment details, passwords, identity verification, or sensitive decisions: do not ask for passwords or stale OTPs up front. Tell the user the call may require live verification and offer options:
task is the API field name. Call instructions are the product concept.
Write the Call instructions like a briefing memo:
Add personality, greeting, and voice only when useful or explicitly specified. Defaults are good. Personality is style, not the call task. Voices: jessica (default, female), sarah (female), chris (male), eric (male).
Use examples for rich task shapes.
POST /call
Content-Type: application/json
X-Api-Key: clawcall_sk_...Only to and task are required. Include bridge_number only for live handoff.
Response includes:
{
"call_id": "ba645d75-...",
"status": "queued",
"api_key": "clawcall_sk_..."
}Save api_key if present.
Poll every 3 seconds:
GET /call/{call_id}
X-Api-Key: clawcall_sk_...Poll until lifecycle = "finalized". Lifecycle values are queued, dialing, answered, finalized.
Terminal responses include outcome, talk_seconds, transcript, and recording_url. outcome is phone-network outcome, not task success. An answered call can still fail to accomplish the user's goal. Read the transcript before reporting.
Cancel/hang up:
POST /call/{call_id}/hangup
X-Api-Key: clawcall_sk_...Lead with the result, not the transcript dump. Include which number was called.
When lifecycle = "finalized":
outcome.Offer transcript, recording, retry, callback, or live handoff when useful.
Do not treat each call as isolated. Keep campaign state across related calls: target, purpose, known facts, constraints, result, blocker, next action, and user decision needed.
Call sooner when safe:
Use the previous transcript in follow-up Call instructions so the phone agent can resume naturally.
Parallel or small-batch calling is useful for option exploration. Use up to 3-4 parallel calls when targets are interchangeable and the call is information-gathering only: restaurants, vendors, appointment availability, inventory checks, or quote gathering.
Do not parallelize when calls can book, buy, cancel, change, approve, or otherwise commit unless the user explicitly gave safe boundaries and duplicate commitments are impossible.
For parallel option searches, every Call instruction must say not to commit unless explicitly allowed, to gather price/availability/timing, to ask how long an option can be held without payment or commitment, and to report back for comparison.
Use live handoff when the user wants to skip hold time, reach a real person, handle identity verification, negotiate, or make real-time decisions.
Ask for the user's own callback number, then include it as bridge_number. The Call instructions must include a clear trigger like: "Once you are speaking with someone who can help, tell them you are connecting Jordan now, then bridge Jordan into the live call."
If a saved user phone number exists, use it as the default bridge_number; confirm only when the call is sensitive, the number may be stale, or the user asks to use a different number. If you collect a new bridge/callback number, persist it.
The transcript covers everything before handoff. After the user joins, the live conversation is private.
Inbound setup configures how ClawCall answers future calls to the user's active reserved number. It is not an outbound call.
Requirements:
Read before editing (the inbound block is null when not entitled):
GET /me/call-preferences
X-Api-Key: clawcall_sk_...Update (voice/personality are global; the inbound assistant goes under inbound):
PUT /me/call-preferences
Content-Type: application/json
X-Api-Key: clawcall_sk_...Top-level voice/personality/greeting are global (also drive outbound) and work for any user. The inbound object requires Reserve Plus + an active reserved number. Inbound required: instructions, greeting. Optional: handoff_number.
handoff_number is structured data. It receives inbound terminal SMS notifications and is the number the voice agent can bridge into an inbound call. It cannot be the user's active reserved number or any ClawCall-owned number. If a saved user phone number exists, offer it as the default handoff_number; persist any new handoff number the user provides.
Clear the inbound assistant. To preserve global voice/personality/greeting, first GET /me/call-preferences, then echo those top-level values in the PUT body:
PUT /me/call-preferences
Content-Type: application/json
X-Api-Key: clawcall_sk_...
{
"voice": "<current voice>",
"personality": "<current personality or null>",
"greeting": "<current greeting or null>",
"inbound": null
}Poll inbound history:
GET /me/calls?direction=inbound&since=<ISO_TIMESTAMP>&limit=25
X-Api-Key: clawcall_sk_...For cron polling, run every 30 minutes, overlap the window, and dedupe by call id. since filters by when the call finalized, not when it started.
Always preserve returned action.url and action.sign_in_url exactly.
invalid_phone: ask for a valid US +1XXXXXXXXXX number.missing_fields: add both to and rich task Call instructions.auth_required / invalid_api_key: ask for a valid key, remove the bad key, or use returned auth URL.quota_exceeded / trial_exhausted / plan_required / balance_depleted: send the returned action URL.number_pool_exhausted / dial_failed / network_error: retry once silently when appropriate.reserved_number_required: user needs Unlimited Reserve Plus with an active reserved number for inbound configuration.inbound_plan_required: Unlimited Reserve Plus is required for inbound calls.invalid_preferences: fix the global voice (must be jessica, sarah, chris, or eric).invalid_profile: fix missing/invalid inbound instructions or greeting.invalid_handoff_number: ask for an external reachable handoff number that is not a ClawCall number.New users get trial access for 10 calls and 10 minutes, whichever lasts later. A trial call counts only after it finalizes with at least 5 seconds of talk time.
Rich details live here:
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.