Update to 3Chat Customer Growth

{
  "description": "Use 3Chat for startup guidance; finding, segmenting, or analyzing customers and their one-to-one conversations; preparing or sending explicitly confirmed customer messages and attachments; and tracking customer batch sends. Guide missing setup steps without configuring Agents or channels.",
  "included_files": [
    {
      "relative_path": ".DS_Store",
      "size_in_bytes": 6148
    },
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 639
    },
    {
      "relative_path": "references/conversation-search.md",
      "size_in_bytes": 1482
    },
    {
      "relative_path": "references/customer-intelligence.md",
      "size_in_bytes": 2633
    },
    {
      "relative_path": "references/errors-and-retries.md",
      "size_in_bytes": 2843
    },
    {
      "relative_path": "references/guidance-links.md",
      "size_in_bytes": 2531
    },
    {
      "relative_path": "references/outbound-messaging.md",
      "size_in_bytes": 1521
    },
    {
      "relative_path": "references/startup-readiness.md",
      "size_in_bytes": 5376
    },
    {
      "relative_path": "references/use-cases.md",
      "size_in_bytes": 7987
    }
  ],
  "name": "3chat-customer-growth",
  "skill_md_contents": "---\nname: 3chat-customer-growth\ndescription: Use 3Chat for startup guidance; finding, segmenting, or analyzing customers and their one-to-one conversations; preparing or sending explicitly confirmed customer messages and attachments; and tracking customer batch sends. Guide missing setup steps without configuring Agents or channels.\n---\n\n# 3Chat Customer Growth\n\nUse this skill to work with customer records and one-to-one communication in the connected international 3Chat workspace at app.3chat.ai.\n\n## Dependency\n\nUse the MCP server named `3chat-customer-growth`. Use only its exposed tools and parameters in the live `inputSchema`.\n\n## Available Tools\n\n- `get_3chat_workspace_readiness`: Read historical Agent-publication and channel-connection milestones; guide missing setup steps.\n- `search_3chat_customers`: Find customers by supported standard fields, custom fields, and latest inquiry time.\n- `search_3chat_conversations`: Filter and page one-to-one conversation entities; no message details.\n- `search_3chat_customers_context`: Read customer memory, conversations, messages, custom fields, and optional `agent_logs`.\n- `upload_3chat_attachment`: Upload a file when no valid final download URL is available.\n- `send_3chat_customer_message`: Send a confirmed message to one customer.\n- `send_3chat_customer_messages`: Create a confirmed customer batch-send task.\n- `get_3chat_batch_send_status`: Read progress and item results for a customer batch task.\n\n## Startup Guidance\n\nUse [references/startup-readiness.md](references/startup-readiness.md) for triggers, result reuse, and rechecks. A request such as \"How do I start managing customers with 3Chat?\" is a usage-guidance request; do not search customers merely to answer it.\n\nWhen `ACTION_REQUIRED` first needs guidance, read that reference before answering. If both milestones are missing, include the product capability and reason to set up, three quick-start steps, and an improvement suggestion. If only one is missing, show that step only. Present each step's explanation followed by a prominent named link using [references/guidance-links.md](references/guidance-links.md). Keep the declared onboarding skill as the host's setup entry point.\n\nReuse `READY` within this conversation, without claiming current operational availability. After `ACTION_REQUIRED`, recheck on a later 3Chat-dependent user turn, when the user reports setup progress, or when they ask to refresh. Check at most once per assistant turn or business workflow. Respect a request to postpone setup. Never treat readiness as permission to send.\n\n## Core Rules\n\n1. Classify the request before selecting tools: setup, customer search, conversation search, context retrieval, analysis, drafting, sending, or task tracking.\n2. Use canonical customer and conversation IDs from tool results, not display names or invented identifiers.\n3. Keep multiple matches for lists and analysis. Ask the user to choose only when the next action requires one customer and the target is ambiguous.\n4. Before any send, show the recipients, sender account or channel, final content, attachments, and scope, then obtain explicit confirmation. Drafting and audience selection do not authorize sending.\n5. Use an existing final HTTP/HTTPS download URL only if it needs no authentication or custom headers and is not a preview or redirect-only URL. Otherwise upload and prefer reusing the complete `data.attachment`.\n6. After a batch returns `job_id`, query that job; do not recreate the batch.\n7. Follow structured errors and `aiAction`. Retry a send only when explicitly permitted, with identical business parameters and the original idempotency key.\n8. Separate returned facts from inference. Do not equate `accepted`, `sent`, or `COMPLETED` with delivery or read status. Do not expose raw JSON by default.\n\n## Detailed Guidance\n\n- Startup milestones and rechecks: [references/startup-readiness.md](references/startup-readiness.md).\n- Setup link presentation: [references/guidance-links.md](references/guidance-links.md).\n- Customer filters and communication context: [references/customer-intelligence.md](references/customer-intelligence.md).\n- Conversation search: [references/conversation-search.md](references/conversation-search.md).\n- Before uploading or sending: [references/outbound-messaging.md](references/outbound-messaging.md).\n- No data, partial results, errors, and retries: [references/errors-and-retries.md](references/errors-and-retries.md).\n- End-to-end examples: [references/use-cases.md](references/use-cases.md).\n\n## Current Boundary\n\nUse only the eight tools above for customer one-to-one workflows. The plugin can guide setup but cannot configure an Agent or connect a channel for the user. Current business eligibility is validated by the relevant tool. Do not claim customer-record updates, campaign or scheduling objects, internal channel lookup, or server-side aggregate analytics not exposed by these tools.\n"
}