What problem does it solve? Managing a centralized multi-tenant chatbot service involves scattered knowledge: editing system prompts in Sanity, provisioning new tenants in Supabase, debugging sync webhooks, and diagnosing why a bot gives wrong answers. This Skill consolidates the operational runbook for the chatbot system hosted at chats.ebecerra.es. ## Core Features & Use Cases - System prompt editing: Patch tenant system prompts in Sanity via MCP or curl mutations, with a validated 10-11 section prompt structure and cache-sync verification. - Tenant provisioning: Generate tenant keys, insert rows into Supabase tenants and chatbot_configs_cache, and wire up the client-side proxy and ChatbotWidget. - Diagnostics: A symptom-to-cause table covering 401 invalid keys, 503 config_not_synced, 429 quota exceeded, stale caches, and webhook fan-out failures. - Use Case: A new external client needs a chatbot. Follow the provisioning steps to generate a key, insert the tenant row, seed the config cache, and hand the client the proxy snippet and env vars. ## Quick Start Ask the assistant to diagnose why a specific tenant's chatbot is responding with outdated information and walk through the cache sync verification steps.