Update to Quickchat AI
Snapshot Nov 9, 2026 · 18:08 UTC · version 2.0.7
Collection source: downloaded plugin package.
Instructions updated for deploy-agent
Full description — Now says: WhatsApp, Slack and Email all start through the tools here, with browser consent and any required setup choices.
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 3 plugins free · no card required.
All fields and original values.
Full description
Oct 25, 2026 · 00:04 UTC
Slack and Email all connect through the tools here, without sending the user to the dashboard.
Nov 9, 2026 · 18:08 UTC
WhatsApp, Slack and Email all start through the tools here, with browser consent and any required setup choices.
Skill instructions
Oct 25, 2026 · 00:04 UTC
Slack and Email all connect through the tools here, without sending the user to the dashboard. Use when the user asks to deploy, publish, go live, share the Agent, embed it on a site, or connect or integrate it with Telegram, Disco...
Nov 9, 2026 · 18:08 UTC
WhatsApp, Slack and Email all start through the tools here, with browser consent and any required setup choices. Use when the user asks to deploy, publish, go live, share the Agent, embed it on a site, or connect or integrate it wi...
Supporting files
Oct 25, 2026 · 00:04 UTC
[{"relative_path":"agents/openai.yaml","size_in_bytes":224}]
Nov 9, 2026 · 18:08 UTC
[{"relative_path":"agents/openai.yaml","size_in_bytes":234}]
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -4,14 +4,15 @@ Put a configured Quickchat AI Agent in front of real users: report which channels are live, then connect the ones the user wants. The website widget, public chat page, the Agent's own MCP endpoint, Discord, Telegram, Instagram, - Slack and Email all connect through the tools here, without sending the user - to the dashboard. Use when the user asks to deploy, publish, go live, share - the Agent, embed it on a site, or connect or integrate it with Telegram, - Discord, Instagram, Slack, email, WhatsApp or any other channel. Not for - building or configuring the Agent itself (use launch-agent or improve-agent). + WhatsApp, Slack and Email all start through the tools here, with browser + consent and any required setup choices. Use when the user asks to deploy, + publish, go live, share the Agent, embed it on a site, or connect or integrate + it with Telegram, Discord, Instagram, Slack, email, WhatsApp or any other + channel. Not for building or configuring the Agent itself (use launch-agent or + improve-agent). metadata: author: quickchat-ai - version: "1.0" + version: "1.1" --- # Deploy an Agent to its channels @@ -25,9 +26,13 @@ 1. Resolve the Agent: call `list_scenarios` and match the name to its `scenario_id`. If several qualify, ask which one. 2. Call `get_deployment_info` and read `channels` — that is the verified state. - A channel listed in `connected` is live; `not_configured` is a definite no; + A channel listed in `connected` has configured routing; + `configured_but_inactive` is set up but not live right now; + `not_configured` is a definite no; `not_checked` (or absent from all four lists) means you could not verify it, so say that rather than guessing. + A configured WhatsApp route does not prove current Meta permissions or + delivery. Ask the user to check an actual reply in WhatsApp. 3. A channel name is never a website. When the user says "connect Telegram" or "put it on Instagram", that is a `connect_agent_channel` call — do NOT scrape telegram.com or instagram.com as a knowledge source, and do NOT @@ -53,9 +58,20 @@ creator) account the Agent should answer DMs for; they sign in with that account and approve message access. This cannot be completed for them: give them the link and tell them which account to sign in with. +- **WhatsApp** (`channel`=whatsapp): returns a one-time link, valid for about + 10 minutes and only for the requesting Quickchat user. They open it signed + in to Quickchat, finish Meta's WhatsApp Embedded Signup and consent, and + complete any business account or phone selection when Quickchat reopens. + Never ask for Meta access tokens in chat. After they finish, read + `get_deployment_info.whatsapp`: `pending_account_selection` means they still + need to choose an account, even if a previous route remains in + `channels.connected`. Ask them to message + the connected number from WhatsApp to check the Agent's reply. Testing with + `send_message_to_agent` does not test WhatsApp delivery. - **Slack** (`channel`=slack): returns a workspace-install link. It needs no - Quickchat sign-in and does not expire, but anyone who opens it can connect - their own workspace to this Agent — pass it only to the intended person. + Quickchat sign-in, so anyone who opens it can connect their own workspace + to this Agent — pass it only to the intended person. It expires in about + 10 minutes; if it lapses, mint a fresh one instead of resending the old link. - **Email** (`channel`=email): provisions the Agent's dedicated inbound address, switches the channel on, and returns `inbound_address`. Mail sent or forwarded there is answered by the Agent; to cover an existing support @@ -72,7 +88,7 @@ `note` saying the surface is switched off and where to enable it. ## Dashboard-only channels -WhatsApp, Facebook Messenger, Intercom, Zendesk and HubSpot are set up on the +Facebook Messenger, Intercom, Zendesk and HubSpot are set up on the Quickchat dashboard's Integrations page, and Shopify from the Shopify App Store or that same page — their setup needs a Meta business login, a page-selection step, a store install, or API credentials that must not travel @@ -83,6 +99,8 @@ 1. After the user says they finished a link flow, call `get_deployment_info` again and confirm the channel moved to `connected` before declaring victory. Discord and Instagram confirm within moments of approval. + For WhatsApp, also check `whatsapp.pending_account_selection` before + reporting setup complete. Delivery needs a real reply in WhatsApp. 2. Offer to test with `send_message_to_agent` — one call sends a real visitor message and returns the reply. It spends an AI credit and can fire the Agent's live AI Actions, so ask before sending.
Full technical diff · 3 changed fields
changed /description
"Put a configured Quickchat AI Agent in front of real users: report which channels are live, then connect the ones the user wants. The website widget, public chat page, the Agent's own MCP endpoint, Discord, Telegram, Instagram, Slack and Email all connect through the tools here, without sending the user to the dashboard. Use when the user asks to deploy, publish, go live, share the Agent, embed it on a site, or connect or integrate it with Telegram, Discord, Instagram, Slack, email, WhatsApp or any other channel. Not for building or configuring the Agent itself (use launch-agent or improve-agent)."
"Put a configured Quickchat AI Agent in front of real users: report which channels are live, then connect the ones the user wants. The website widget, public chat page, the Agent's own MCP endpoint, Discord, Telegram, Instagram, WhatsApp, Slack and Email all start through the tools here, with browser consent and any required setup choices. Use when the user asks to deploy, publish, go live, share the Agent, embed it on a site, or connect or integrate it with Telegram, Discord, Instagram, Slack, email, WhatsApp or any other channel. Not for building or configuring the Agent itself (use launch-agent or improve-agent)."
changed /included_files
[
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 224
}
][
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 234
}
]changed /skill_md_contents
"---\nname: deploy-agent\ndescription: >-\n Put a configured Quickchat AI Agent in front of real users: report which\n channels are live, then connect the ones the user wants. The website widget,\n public chat page, the Agent's own MCP endpoint, Discord, Telegram, Instagram,\n Slack and Email all connect through the tools here, without sending the user\n to the dashboard. Use when the user asks to deploy, publish, go live, share\n the Agent, embed it on a site, or connect or integrate it with Telegram,\n Discord, Instagram, Slack, email, WhatsApp or any other channel. Not for\n building or configuring the Agent itself (use launch-agent or improve-agent).\nmetadata:\n author: quickchat-ai\n version: \"1.0\"\n---\n\n# Deploy an Agent to its channels\n\nConnecting a channel is tool work, not dashboard homework. Every channel below\nhas a first-class path through `connect_agent_channel`; only the ones under\n\"Dashboard-only channels\" need the Quickchat dashboard, and you say so exactly\nonce instead of guessing.\n\n## Before you start\n1. Resolve the Agent: call `list_scenarios` and match the name to its\n `scenario_id`. If several qualify, ask which one.\n2. Call `get_deployment_info` and read `channels` — that is the verified state.\n A channel listed in `connected` is live; `not_configured` is a definite no;\n `not_checked` (or absent from all four lists) means you could not verify it,\n so say that rather than guessing.\n3. A channel name is never a website. When the user says \"connect Telegram\" or\n \"put it on Instagram\", that is a `connect_agent_channel` call — do NOT\n scrape telegram.com or instagram.com as a knowledge source, and do NOT\n describe dashboard menus for a channel this tool connects.\n\n## Connecting each channel\nAll of these are `connect_agent_channel` with the right `channel` value. Relay\nthe returned `instructions` faithfully — they say who may open a link and for\nhow long it works.\n\n- **Telegram** (`channel`=telegram): switches on the Agent's direct-message\n link and returns it. The link is durable and shareable — ideal for a personal\n assistant. Telegram groups are the one Telegram case that needs the\n dashboard.\n- **Discord** (`channel`=discord, optional `nickname`): returns a one-time\n link. The user opens it in a browser where they are signed in to Quickchat,\n picks the server, and approves. It works once, only for them, and expires in\n about 10 minutes (`expires_in_seconds` is authoritative) — if it lapses,\n mint a fresh one instead of resending the old link.\n- **Instagram** (`channel`=instagram): returns a one-time link like Discord's.\n It forwards to Instagram, which always asks the user to sign in (even with a\n session already open) so they can choose the professional (business or\n creator) account the Agent should answer DMs for; they sign in with that\n account and approve message access. This cannot be completed for them: give\n them the link and tell them which account to sign in with.\n- **Slack** (`channel`=slack): returns a workspace-install link. It needs no\n Quickchat sign-in and does not expire, but anyone who opens it can connect\n their own workspace to this Agent — pass it only to the intended person.\n- **Email** (`channel`=email): provisions the Agent's dedicated inbound\n address, switches the channel on, and returns `inbound_address`. Mail sent\n or forwarded there is answered by the Agent; to cover an existing support\n inbox, the user forwards that inbox to this address.\n- **The Agent's own MCP endpoint** (`channel`=mcp with `is_active`=true):\n lets ChatGPT, Claude or Cursor users add the Agent as a connector.\n `visibility` public means anyone with the URL, private requires signing in.\n Switching it OFF (`is_active`=false) disconnects existing users, so ask\n before doing that. Plans without the MCP channel are refused — relay the\n upgrade message rather than retrying.\n- **Website widget and public chat page**: no connect call — read\n `website_widget` and `public_chat_page` from `get_deployment_info` and hand\n over `embed_snippet` (paste before `</body>`) or the page URL, plus any\n `note` saying the surface is switched off and where to enable it.\n\n## Dashboard-only channels\nWhatsApp, Facebook Messenger, Intercom, Zendesk and HubSpot are set up on the\nQuickchat dashboard's Integrations page, and Shopify from the Shopify App\nStore or that same page — their setup needs a Meta business login, a\npage-selection step, a store install, or API credentials that must not travel\nthrough chat. Say where they are set up, and read `channels` for whether they\nalready are; never present a dashboard path for the channels listed above.\n\n## Verify and close\n1. After the user says they finished a link flow, call `get_deployment_info`\n again and confirm the channel moved to `connected` before declaring\n victory. Discord and Instagram confirm within moments of approval.\n2. Offer to test with `send_message_to_agent` — one call sends a real visitor\n message and returns the reply. It spends an AI credit and can fire the\n Agent's live AI Actions, so ask before sending.\n3. Close with what is now live and one next step (another channel, or\n improve-agent for tuning).\n\n## Guardrails\n- Mint links on demand, one per request: connect links are throttled per user,\n so never loop `connect_agent_channel` retrying the same channel.\n- If the tool answers that a channel is temporarily unavailable, relay that\n message and try again in a few minutes; do not fall back to inventing\n dashboard steps or scraping websites.\n- A lapsed or refused link is replaced by calling the tool again, never by\n editing the URL.\n"
"---\nname: deploy-agent\ndescription: >-\n Put a configured Quickchat AI Agent in front of real users: report which\n channels are live, then connect the ones the user wants. The website widget,\n public chat page, the Agent's own MCP endpoint, Discord, Telegram, Instagram,\n WhatsApp, Slack and Email all start through the tools here, with browser\n consent and any required setup choices. Use when the user asks to deploy,\n publish, go live, share the Agent, embed it on a site, or connect or integrate\n it with Telegram, Discord, Instagram, Slack, email, WhatsApp or any other\n channel. Not for building or configuring the Agent itself (use launch-agent or\n improve-agent).\nmetadata:\n author: quickchat-ai\n version: \"1.1\"\n---\n\n# Deploy an Agent to its channels\n\nConnecting a channel is tool work, not dashboard homework. Every channel below\nhas a first-class path through `connect_agent_channel`; only the ones under\n\"Dashboard-only channels\" need the Quickchat dashboard, and you say so exactly\nonce instead of guessing.\n\n## Before you start\n1. Resolve the Agent: call `list_scenarios` and match the name to its\n `scenario_id`. If several qualify, ask which one.\n2. Call `get_deployment_info` and read `channels` — that is the verified state.\n A channel listed in `connected` has configured routing;\n `configured_but_inactive` is set up but not live right now;\n `not_configured` is a definite no;\n `not_checked` (or absent from all four lists) means you could not verify it,\n so say that rather than guessing.\n A configured WhatsApp route does not prove current Meta permissions or\n delivery. Ask the user to check an actual reply in WhatsApp.\n3. A channel name is never a website. When the user says \"connect Telegram\" or\n \"put it on Instagram\", that is a `connect_agent_channel` call — do NOT\n scrape telegram.com or instagram.com as a knowledge source, and do NOT\n describe dashboard menus for a channel this tool connects.\n\n## Connecting each channel\nAll of these are `connect_agent_channel` with the right `channel` value. Relay\nthe returned `instructions` faithfully — they say who may open a link and for\nhow long it works.\n\n- **Telegram** (`channel`=telegram): switches on the Agent's direct-message\n link and returns it. The link is durable and shareable — ideal for a personal\n assistant. Telegram groups are the one Telegram case that needs the\n dashboard.\n- **Discord** (`channel`=discord, optional `nickname`): returns a one-time\n link. The user opens it in a browser where they are signed in to Quickchat,\n picks the server, and approves. It works once, only for them, and expires in\n about 10 minutes (`expires_in_seconds` is authoritative) — if it lapses,\n mint a fresh one instead of resending the old link.\n- **Instagram** (`channel`=instagram): returns a one-time link like Discord's.\n It forwards to Instagram, which always asks the user to sign in (even with a\n session already open) so they can choose the professional (business or\n creator) account the Agent should answer DMs for; they sign in with that\n account and approve message access. This cannot be completed for them: give\n them the link and tell them which account to sign in with.\n- **WhatsApp** (`channel`=whatsapp): returns a one-time link, valid for about\n 10 minutes and only for the requesting Quickchat user. They open it signed\n in to Quickchat, finish Meta's WhatsApp Embedded Signup and consent, and\n complete any business account or phone selection when Quickchat reopens.\n Never ask for Meta access tokens in chat. After they finish, read\n `get_deployment_info.whatsapp`: `pending_account_selection` means they still\n need to choose an account, even if a previous route remains in\n `channels.connected`. Ask them to message\n the connected number from WhatsApp to check the Agent's reply. Testing with\n `send_message_to_agent` does not test WhatsApp delivery.\n- **Slack** (`channel`=slack): returns a workspace-install link. It needs no\n Quickchat sign-in, so anyone who opens it can connect their own workspace\n to this Agent — pass it only to the intended person. It expires in about\n 10 minutes; if it lapses, mint a fresh one instead of resending the old link.\n- **Email** (`channel`=email): provisions the Agent's dedicated inbound\n address, switches the channel on, and returns `inbound_address`. Mail sent\n or forwarded there is answered by the Agent; to cover an existing support\n inbox, the user forwards that inbox to this address.\n- **The Agent's own MCP endpoint** (`channel`=mcp with `is_active`=true):\n lets ChatGPT, Claude or Cursor users add the Agent as a connector.\n `visibility` public means anyone with the URL, private requires signing in.\n Switching it OFF (`is_active`=false) disconnects existing users, so ask\n before doing that. Plans without the MCP channel are refused — relay the\n upgrade message rather than retrying.\n- **Website widget and public chat page**: no connect call — read\n `website_widget` and `public_chat_page` from `get_deployment_info` and hand\n over `embed_snippet` (paste before `</body>`) or the page URL, plus any\n `note` saying the surface is switched off and where to enable it.\n\n## Dashboard-only channels\nFacebook Messenger, Intercom, Zendesk and HubSpot are set up on the\nQuickchat dashboard's Integrations page, and Shopify from the Shopify App\nStore or that same page — their setup needs a Meta business login, a\npage-selection step, a store install, or API credentials that must not travel\nthrough chat. Say where they are set up, and read `channels` for whether they\nalready are; never present a dashboard path for the channels listed above.\n\n## Verify and close\n1. After the user says they finished a link flow, call `get_deployment_info`\n again and confirm the channel moved to `connected` before declaring\n victory. Discord and Instagram confirm within moments of approval.\n For WhatsApp, also check `whatsapp.pending_account_selection` before\n reporting setup complete. Delivery needs a real reply in WhatsApp.\n2. Offer to test with `send_message_to_agent` — one call sends a real visitor\n message and returns the reply. It spends an AI credit and can fire the\n Agent's live AI Actions, so ask before sending.\n3. Close with what is now live and one next step (another channel, or\n improve-agent for tuning).\n\n## Guardrails\n- Mint links on demand, one per request: connect links are throttled per user,\n so never loop `connect_agent_channel` retrying the same channel.\n- If the tool answers that a channel is temporarily unavailable, relay that\n message and try again in a few minutes; do not fall back to inventing\n dashboard steps or scraping websites.\n- A lapsed or refused link is replaced by calling the tool again, never by\n editing the URL.\n"
Full snapshot data
{
"description": "Put a configured Quickchat AI Agent in front of real users: report which channels are live, then connect the ones the user wants. The website widget, public chat page, the Agent's own MCP endpoint, Discord, Telegram, Instagram, WhatsApp, Slack and Email all start through the tools here, with browser consent and any required setup choices. Use when the user asks to deploy, publish, go live, share the Agent, embed it on a site, or connect or integrate it with Telegram, Discord, Instagram, Slack, email, WhatsApp or any other channel. Not for building or configuring the Agent itself (use launch-agent or improve-agent).",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 234
}
],
"name": "deploy-agent",
"skill_md_contents": "---\nname: deploy-agent\ndescription: >-\n Put a configured Quickchat AI Agent in front of real users: report which\n channels are live, then connect the ones the user wants. The website widget,\n public chat page, the Agent's own MCP endpoint, Discord, Telegram, Instagram,\n WhatsApp, Slack and Email all start through the tools here, with browser\n consent and any required setup choices. Use when the user asks to deploy,\n publish, go live, share the Agent, embed it on a site, or connect or integrate\n it with Telegram, Discord, Instagram, Slack, email, WhatsApp or any other\n channel. Not for building or configuring the Agent itself (use launch-agent or\n improve-agent).\nmetadata:\n author: quickchat-ai\n version: \"1.1\"\n---\n\n# Deploy an Agent to its channels\n\nConnecting a channel is tool work, not dashboard homework. Every channel below\nhas a first-class path through `connect_agent_channel`; only the ones under\n\"Dashboard-only channels\" need the Quickchat dashboard, and you say so exactly\nonce instead of guessing.\n\n## Before you start\n1. Resolve the Agent: call `list_scenarios` and match the name to its\n `scenario_id`. If several qualify, ask which one.\n2. Call `get_deployment_info` and read `channels` — that is the verified state.\n A channel listed in `connected` has configured routing;\n `configured_but_inactive` is set up but not live right now;\n `not_configured` is a definite no;\n `not_checked` (or absent from all four lists) means you could not verify it,\n so say that rather than guessing.\n A configured WhatsApp route does not prove current Meta permissions or\n delivery. Ask the user to check an actual reply in WhatsApp.\n3. A channel name is never a website. When the user says \"connect Telegram\" or\n \"put it on Instagram\", that is a `connect_agent_channel` call — do NOT\n scrape telegram.com or instagram.com as a knowledge source, and do NOT\n describe dashboard menus for a channel this tool connects.\n\n## Connecting each channel\nAll of these are `connect_agent_channel` with the right `channel` value. Relay\nthe returned `instructions` faithfully — they say who may open a link and for\nhow long it works.\n\n- **Telegram** (`channel`=telegram): switches on the Agent's direct-message\n link and returns it. The link is durable and shareable — ideal for a personal\n assistant. Telegram groups are the one Telegram case that needs the\n dashboard.\n- **Discord** (`channel`=discord, optional `nickname`): returns a one-time\n link. The user opens it in a browser where they are signed in to Quickchat,\n picks the server, and approves. It works once, only for them, and expires in\n about 10 minutes (`expires_in_seconds` is authoritative) — if it lapses,\n mint a fresh one instead of resending the old link.\n- **Instagram** (`channel`=instagram): returns a one-time link like Discord's.\n It forwards to Instagram, which always asks the user to sign in (even with a\n session already open) so they can choose the professional (business or\n creator) account the Agent should answer DMs for; they sign in with that\n account and approve message access. This cannot be completed for them: give\n them the link and tell them which account to sign in with.\n- **WhatsApp** (`channel`=whatsapp): returns a one-time link, valid for about\n 10 minutes and only for the requesting Quickchat user. They open it signed\n in to Quickchat, finish Meta's WhatsApp Embedded Signup and consent, and\n complete any business account or phone selection when Quickchat reopens.\n Never ask for Meta access tokens in chat. After they finish, read\n `get_deployment_info.whatsapp`: `pending_account_selection` means they still\n need to choose an account, even if a previous route remains in\n `channels.connected`. Ask them to message\n the connected number from WhatsApp to check the Agent's reply. Testing with\n `send_message_to_agent` does not test WhatsApp delivery.\n- **Slack** (`channel`=slack): returns a workspace-install link. It needs no\n Quickchat sign-in, so anyone who opens it can connect their own workspace\n to this Agent — pass it only to the intended person. It expires in about\n 10 minutes; if it lapses, mint a fresh one instead of resending the old link.\n- **Email** (`channel`=email): provisions the Agent's dedicated inbound\n address, switches the channel on, and returns `inbound_address`. Mail sent\n or forwarded there is answered by the Agent; to cover an existing support\n inbox, the user forwards that inbox to this address.\n- **The Agent's own MCP endpoint** (`channel`=mcp with `is_active`=true):\n lets ChatGPT, Claude or Cursor users add the Agent as a connector.\n `visibility` public means anyone with the URL, private requires signing in.\n Switching it OFF (`is_active`=false) disconnects existing users, so ask\n before doing that. Plans without the MCP channel are refused — relay the\n upgrade message rather than retrying.\n- **Website widget and public chat page**: no connect call — read\n `website_widget` and `public_chat_page` from `get_deployment_info` and hand\n over `embed_snippet` (paste before `</body>`) or the page URL, plus any\n `note` saying the surface is switched off and where to enable it.\n\n## Dashboard-only channels\nFacebook Messenger, Intercom, Zendesk and HubSpot are set up on the\nQuickchat dashboard's Integrations page, and Shopify from the Shopify App\nStore or that same page — their setup needs a Meta business login, a\npage-selection step, a store install, or API credentials that must not travel\nthrough chat. Say where they are set up, and read `channels` for whether they\nalready are; never present a dashboard path for the channels listed above.\n\n## Verify and close\n1. After the user says they finished a link flow, call `get_deployment_info`\n again and confirm the channel moved to `connected` before declaring\n victory. Discord and Instagram confirm within moments of approval.\n For WhatsApp, also check `whatsapp.pending_account_selection` before\n reporting setup complete. Delivery needs a real reply in WhatsApp.\n2. Offer to test with `send_message_to_agent` — one call sends a real visitor\n message and returns the reply. It spends an AI credit and can fire the\n Agent's live AI Actions, so ask before sending.\n3. Close with what is now live and one next step (another channel, or\n improve-agent for tuning).\n\n## Guardrails\n- Mint links on demand, one per request: connect links are throttled per user,\n so never loop `connect_agent_channel` retrying the same channel.\n- If the tool answers that a channel is temporarily unavailable, relay that\n message and try again in a few minutes; do not fall back to inventing\n dashboard steps or scraping websites.\n- A lapsed or refused link is replaced by calling the tool again, never by\n editing the URL.\n"
}SHA-256 of public snapshot: bc19a48fd5dd276fac23053f5de6cfd166008924acb1735330438c6b63bd9350