Update to Phonic

{
  "description": "Steer a live Phonic voice conversation with system messages, tool availability, and reply controls. Use when adding app context mid-call or controlling when an agent speaks.",
  "included_files": [],
  "name": "phonic-steering",
  "skill_md_contents": "---\nname: phonic-steering\ndescription: Steer a live Phonic voice conversation with system messages, tool availability, and reply controls. Use when adding app context mid-call or controlling when an agent speaks.\nlicense: MIT\n---\n\n# Steer a live Phonic conversation\n\nRead the relevant message schemas in [AsyncAPI](https://docs.phonic.ai/asyncapi.json) and the [WebSocket guide](https://docs.phonic.ai/docs/build/with-web-sockets/via-web-sockets.md). Send control messages on the active conversation's STS WebSocket or the application's SDK connection. The inbound API MCP and the read-only live monitoring socket are not substitutes for that connection.\n\nChoose the control matching the user's intent:\n\n- **Add new context or instructions:** `add_system_message`. This is the current message name; there is no `add_system_prompt` message. `update_system_prompt` is deprecated.\n- **Change available tools:** `update_tools_subset`, using the documented list shape. Verify which tools remain available before sending the new subset.\n- **Request a reply now:** `generate_reply`; adding context and requesting speech are distinct operations.\n- **Speak specified text:** `say`, using the current schema rather than assuming it accepts the same fields as a system message.\n- **Change future conversations:** update the saved agent configuration instead of treating a live control message as a persistent prompt edit.\n\nFor example, after the conversation has been configured:\n\n```json\n{\n  \"type\": \"add_system_message\",\n  \"system_message\": \"The user has selected the annual plan in the app. Explain the annual plan if they ask about their selection.\"\n}\n```\n\nOnly follow that with `generate_reply` when the app should proactively speak. Keep trusted application instructions separate from untrusted user/document text. Do not place API keys or unnecessary personal data in the message.\n\nVerify the intended effect in the transcript and tool events, including what happens if the user is speaking when the update arrives. Keep the audio loop nonblocking. Report the distinction between a successfully sent message and observed agent behavior; sending a control message is not proof the agent followed it.\n"
}