Update to CALL-E

{
  "description": "Use CALL-E to prepare a single phone call for user confirmation, reopen its card, check its status or result, and read its transcript.",
  "included_files": [],
  "name": "agentic-call",
  "skill_md_contents": "---\nname: agentic-call\ndescription: Use CALL-E to prepare a single phone call for user confirmation, reopen its card, check its status or result, and read its transcript.\n---\n\n# CALL-E Agentic calling\n\nUse this workflow for CALL-E phone tasks. Use only the four tools below. If a required tool is unavailable, explain that the Agentic workflow is not available yet; do not fall back to a legacy calling tool or a separate dialing API.\n\n| User intent | Tool |\n| --- | --- |\n| Prepare, revise, or reopen a preparation | `prepare_call` |\n| Reopen an existing confirmed call and its card | `open_call` |\n| Check an existing call's status or result | `get_call` |\n| Read what was said on an existing call | `get_call_transcript` |\n\n## Prepare and confirm\n\n1. Call `prepare_call` with the user's `task` and only known facts. Include `phone`, `region`, or spoken-language `locale` only when supplied or confirmed. Never invent phone numbers, facts, clarification questions, or readiness.\n2. Show the real CALL-E card and its server-provided questions. Do not replace the card with a model-generated form. Preparing a card does not dial.\n3. To reopen an unsubmitted preparation, pass its returned `preparation_id`. To revise it from chat, pass that `preparation_id`, the current `revision`, and the user's correction or answer as `user_input`. Use the newly returned revision after an edit; do not create a duplicate preparation.\n4. The user must review and confirm the latest ready revision by clicking Dial in the card. A chat request, a ready status, or a prepared card is not a substitute for that click. Never invoke a dialing endpoint or another tool to bypass confirmation.\n5. If reopening a submitted preparation returns its existing call, continue with that call. Do not create or dial a replacement automatically. If the preparation has expired, explain this and prepare a new card only for the user's current request; confirmation is still required.\n\n## Follow an existing call\n\nUse the actual `call_id` returned by CALL-E for `open_call`, `get_call`, and `get_call_transcript`. Keep preparation IDs and call IDs distinct. Do not convert old plan IDs, confirmation tokens, or run IDs into call IDs, and do not invent an ID. If no call ID is available in the conversation, ask the user for it.\n\nUse `open_call` when the user wants the call card and its controls. It does not place another call. Cancellation is also a user action in the card when that control is available.\n\nUse `get_call` for status and results. Poll only while `result_status` is `pending`; `unavailable` and `not_applicable` are final even if `result` and `error` are null. Treat no-answer, busy, and declined as reported call outcomes, not automatically as technical failures. Never redial automatically.\n\nUse `get_call_transcript` for the available conversation text. Do not invent dialogue or infer that no call occurred when a transcript is missing.\n\n## Scope\n\nThis workflow supports one immediate phone task at a time. Do not promise scheduled execution or batch calls. Keep user-facing explanations brief and let the card present required questions, confirmation, progress, and results. Never claim a call started or completed without supporting tool or card state.\n"
}