Update to BiglySales

{
  "description": "Use when the user first connects BiglySales or asks to set up, review or change their AI sales assistant (voice, SMS, follow-ups, web calling).",
  "included_files": [],
  "name": "get-started",
  "skill_md_contents": "---\nname: get-started\ndescription: Use when the user first connects BiglySales or asks to set up, review or change their AI sales assistant (voice, SMS, follow-ups, web calling).\n---\n\n# Getting started with BiglySales\n\nBiglySales reads and configures the AI assistant of the workspace the user signed in to. Subscription, plan and billing changes aren't available here. If the user asks for one, tell them it's managed in the BiglySales app, without upgrade links or pricing.\n\n## First steps\n\n1. Before the first change, call `tenant_ai_onboarding_guide`. Settle its questions with the user before you change anything.\n2. Check the workspace type (`bigly://tenant/ai-config`, `tenant.type`):\n   - **telephony**: phone numbers, SIP, SMS agents, DNC and call/message follow-ups apply.\n   - **web_call** (Talk Kit): no phone numbers or SMS. Web Calling, the voice prompt and the intro matter. Don't propose SMS agents or call/message follow-ups.\n\n## Making changes\n\nEvery area has a read tool `tenant_ai_<area>` and a write tool `tenant_ai_<area>_update`.\n\n1. Read the current values with the read tool.\n2. Call the write tool with `preview_update` and show the user the diff.\n3. Only after the user explicitly confirms, call `apply_update` with the same values and the confirmation string. `apply_update` is refused without a matching preview.\n\nNever skip the preview, even if the user asks you to.\n\n## Useful checks\n\n- To verify an intro, company-variable or voice-prompt change, use `tenant_ai_call_context_preview` (`call_type=\"web\"` for a browser call). It doesn't dial.\n- Never ask the user for passwords, tokens, API keys or other credentials, and never pass them to a tool. Webhook credentials and credential settings are set in the BiglySales app; here they always come back masked and are kept unchanged.\n- Credit score values come back masked in call previews. Don't try to work them out.\n- An empty `allowed_domains` on Web Calling blocks every embed. `regenerate_token` breaks every snippet that's already deployed, so warn the user first.\n"
}