Update to ThunderPhone

{
  "description": "Find out why something in ThunderPhone is not working, from evidence: a number that does not ring through, a campaign that does not call, a webhook that does not arrive, or an agent that behaves wrongly. Use when someone reports a problem or asks for a person.",
  "included_files": [],
  "name": "troubleshoot",
  "skill_md_contents": "---\nname: troubleshoot\ndescription: Find out why something in ThunderPhone is not working, from evidence: a number that does not ring through, a campaign that does not call, a webhook that does not arrive, or an agent that behaves wrongly. Use when someone reports a problem or asks for a person.\nlicense: MIT\ncompatibility: Requires the ThunderPhone MCP server, connected with OAuth. No step asks for a password, API key or other secret.\nmetadata:\n  author: thunderphone\n  version: \"1.0\"\n---\n\n# Troubleshoot\n\nBase every claim on what a tool returns, and name the evidence.\n\n| Problem | Start with |\n|---|---|\n| Calls to a number fail | `check_phone_number` with the number as dialed |\n| A campaign does not call | `check_campaign` |\n| A webhook did not arrive | `list_webhook_deliveries` |\n| \"Can it do X?\" or \"what is the limit?\" | `get_agent_capabilities`, `get_account_limits`, `search_docs` |\n| An agent says the wrong thing | `get_call_insights`, then `test_in_text` |\n\n- Run the check again after the user changes anything.\n- A setting change the user asks for goes on the draft first; deploy after a yes.\n- Use `escalate_to_human` for a suspected bug, a billing question or when the user\n  asks for a person. Summarize the problem without call content or caller\n  details. Use `request_feature` when ThunderPhone cannot do something yet,\n  after asking what the user needs it for.\n\nDocs: https://thunderphone.com/docs/guides/issues\n"
}