Update to AppDeploy
Snapshot Nov 20, 2026 · 18:10 UTC · version 3.0.3
Collection source: downloaded plugin package.
Instructions updated for onboarding
Skill instructions — Now says: Sign-in routing: When the host supports widgets, use sign_in and let the user click Sign in; do not call begin_sign_in directly for the initial request....
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.
Skill instructions
Nov 1, 2026 · 18:10 UTC
Ask exactly one question: "What would you like to build?" Supply exactly two selectable options: the two suggested app titles. The user's own idea belongs in the chooser's built-in free-text answer field, which is provided automatically....
Nov 20, 2026 · 18:10 UTC
Sign-in routing: When the host supports widgets, use sign_in and let the user click Sign in; do not call begin_sign_in directly for the initial request. Exception: if the widget posts the follow-up "AppDeploy widget sign-in couldn't star...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -7,6 +7,16 @@ Run onboarding directly in the conversation. Do not call `appdeploy_onboarding` or open the onboarding widget. +Sign-in routing: When the host supports widgets, use sign_in and let the user click Sign in; do not call begin_sign_in directly for the initial request. Exception: if the widget posts the follow-up "AppDeploy widget sign-in couldn't start. Call begin_sign_in directly, then appdeploy_who_am_i to verify the connected account. Do not show another sign-in widget or ask for another chat confirmation.", call begin_sign_in directly even on a widget-capable host. The button click already authorized sign-in: do not show another widget, ask for another chat confirmation, or retry through the widget. After reconnection call appdeploy_who_am_i and verify the connected account. For the initial request, call begin_sign_in directly only on a host without widget support, after the user explicitly requests sign-in or selects Sign in. The initial instructions below to call `sign_in` apply to hosts that support widgets. Honor the widget-failure exception above if its button cannot start browser sign-in. + +Before suggesting app ideas or showing the chooser, call `appdeploy_who_am_i` with `{"profile_only":true}`. Do not supply a subject, email, or user ID as a tool argument. + +Use the returned `isGuest` boolean to decide whether to offer sign-in. If whoami fails or does not return a boolean, retry the account check once; if it still fails, explain that account status is unavailable and stop onboarding. Do not infer guest status from a missing email or the subject association flag. + +If `isGuest: true` and `has_associated_registered_account: true`, this is a returning user whose current connection is still a guest. Immediately call `sign_in` with `{"context":"onboarding"}` to show the personalized Welcome back widget. The sign-in tool looks up the associated email server-side; do not request or pass an email. Do not suggest app ideas or show the multi-select. Wait for verified sign-in, then call `appdeploy_who_am_i` again to verify the connected account and show its apps. If sign-in is cancelled or rejected, keep the sign-in flow pending; do not show the ideas chooser or start a deployment. + +Otherwise continue with the chooser below. For `isGuest: true`, offer two ideas, sign in, and the custom-answer field, including guests who intend to sign in to an unassociated legacy account. For `isGuest: false`, offer only two ideas and the custom-answer field: this user is already signed in, so omit the sign-in option and do not call a sign-in tool during onboarding. Subject recognition must never switch accounts or start authentication automatically. If whoami reports a subject conflict involving another guest, keep sign-in available for the existing guest recovery flow. + ## Choose the starting point Start with what you already know about the user from previous conversations and saved memories to understand their interests, recurring activities, and needs. Use the host's memory or conversation-history retrieval capabilities when available and needed to recall relevant information. Supplement this with any current conversation context. A new or empty chat is not sufficient reason to skip personalization. @@ -19,21 +29,21 @@ After presenting the two suggested apps, call the host's native multiple-choice/ask-user tool in the same turn. Use `request_user_input_async` when available, otherwise use a compatible native tool such as `request_user_input`. Do not stop with only a question in chat or switch modes to ask it. -Ask exactly one question: "What would you like to build?" Supply exactly two selectable options: the two suggested app titles. The user's own idea belongs in the chooser's built-in free-text answer field, which is provided automatically. Leave that field empty for the user; do not add "Custom idea", "Your own app idea", "Other", or an input placeholder as a selectable option. +Ask exactly one question: "What would you like to build?" Supply the two suggested app titles in order. Only when `isGuest: true`, append "I have apps, sign in" as the third selectable option, using that exact label. When `isGuest: false`, supply exactly two selectable options. The user's own idea belongs in the chooser's built-in free-text answer field, which is provided automatically. Leave that field empty for the user; do not add "Custom idea", "Your own app idea", "Other", or an input placeholder as a selectable option. -For `request_user_input_async`, use this payload shape, replacing the suggested titles: +For `request_user_input_async`, use this guest payload shape, replacing the suggested titles. For registered users, remove the third option: - {"questions":[{"title":"What would you like to build?","options":["<first app title>","<second app title>"]}]} + {"questions":[{"title":"What would you like to build?","options":["<first app title>","<second app title>","I have apps, sign in"]}]} -For `request_user_input`, use its question and option-object schema: +For `request_user_input`, use its question and option-object schema with the same guest condition. For registered users, remove the third option: - {"questions":[{"header":"App idea","id":"app_idea","question":"What would you like to build?","options":[{"label":"<first app title>","description":"<first app purpose>"},{"label":"<second app title>","description":"<second app purpose>"}]}]} + {"questions":[{"header":"App idea","id":"app_idea","question":"What would you like to build?","options":[{"label":"<first app title>","description":"<first app purpose>"},{"label":"<second app title>","description":"<second app purpose>"},{"label":"I have apps, sign in","description":"Sign in to continue with your existing AppDeploy apps"}]}]} -For either tool, the options array must contain exactly two app ideas. For another native ask-user tool, apply the same two-option and built-in free-text-field interaction using its supported schema. +For another native ask-user tool, apply the same account-dependent options and built-in free-text-field interaction using its supported schema. -If no native chooser supports this interaction, show both suggested app titles in chat and ask the user to choose one or describe their own idea. +If no native chooser supports this interaction, show both suggested app titles in chat, include the sign-in choice only for guests, and ask the user to choose one or describe their own idea. -Wait for an explicit selection or a non-empty custom idea before building anything. A preselected option, an unanswered question, or a dismissed chooser is not a choice. +Wait for an explicit selection or a non-empty custom idea before building anything or starting authentication. A preselected option, an unanswered question, or a dismissed chooser is not a choice. ## Build and deploy @@ -42,3 +52,20 @@ If the user provides their own idea, use that as the build request. Fill in routine implementation details without adding unrelated features. For either path, proceed to build and deploy the chosen app with AppDeploy, starting with `get_deploy_instructions` and following the returned workflow. Do not stop after presenting the build prompt or ask the user to repeat their selection. + +## Sign in + +If the user selects sign-in in the native chooser, call `sign_in` +with `{"context":"onboarding"}` immediately to show the Welcome back widget. Do not ask for another chat confirmation. +Wait for successful sign-in/reconnection, +then call `appdeploy_who_am_i` to verify the connected account and show its apps. +If sign-in is cancelled or fails, do not claim it succeeded or deploy an app. + +For a separate typed request such as "sign in", call `sign_in` with +`{"context":"requested"}` immediately. Do not ask the user to repeat or confirm +that request. The widget button starts browser sign-in. After successful +sign-in/reconnection, call `appdeploy_who_am_i` to verify the connected account. +If a sign_in_outcome reports a rejection, explain its message without claiming success. + +If a required AppDeploy tool is unavailable, explain that its MCP connection needs +to be refreshed. Keep accompanying messages brief.
Full technical diff · 1 changed fields
changed /skill_md_contents
"---\n{\n \"name\": \"onboarding\",\n \"description\": \"Help users get started with AppDeploy by suggesting two personalized app ideas or collecting their own, then building and deploying their choice. Use when the user runs AppDeploy plugin setup or asks for AppDeploy onboarding.\"\n}\n---\n\nRun onboarding directly in the conversation. Do not call `appdeploy_onboarding` or open the onboarding widget.\n\n## Choose the starting point\n\nStart with what you already know about the user from previous conversations and saved memories to understand their interests, recurring activities, and needs. Use the host's memory or conversation-history retrieval capabilities when available and needed to recall relevant information. Supplement this with any current conversation context. A new or empty chat is not sufficient reason to skip personalization.\n\nSuggest exactly two distinct apps that match the user's interests, serve useful purposes, and are simple enough to build quickly. Give each a short, concrete title that names its main function, such as \"Shopping list planner\", \"Chat with friends\", or \"Calorie tracker\".\n\nOnly if neither prior knowledge nor current conversation context provides enough information to suggest useful, personalized ideas, suggest exactly two useful utility apps instead.\n\n## Ask for a choice\n\nAfter presenting the two suggested apps, call the host's native multiple-choice/ask-user tool in the same turn. Use `request_user_input_async` when available, otherwise use a compatible native tool such as `request_user_input`. Do not stop with only a question in chat or switch modes to ask it.\n\nAsk exactly one question: \"What would you like to build?\" Supply exactly two selectable options: the two suggested app titles. The user's own idea belongs in the chooser's built-in free-text answer field, which is provided automatically. Leave that field empty for the user; do not add \"Custom idea\", \"Your own app idea\", \"Other\", or an input placeholder as a selectable option.\n\nFor `request_user_input_async`, use this payload shape, replacing the suggested titles:\n\n {\"questions\":[{\"title\":\"What would you like to build?\",\"options\":[\"<first app title>\",\"<second app title>\"]}]}\n\nFor `request_user_input`, use its question and option-object schema:\n\n {\"questions\":[{\"header\":\"App idea\",\"id\":\"app_idea\",\"question\":\"What would you like to build?\",\"options\":[{\"label\":\"<first app title>\",\"description\":\"<first app purpose>\"},{\"label\":\"<second app title>\",\"description\":\"<second app purpose>\"}]}]}\n\nFor either tool, the options array must contain exactly two app ideas. For another native ask-user tool, apply the same two-option and built-in free-text-field interaction using its supported schema.\n\nIf no native chooser supports this interaction, show both suggested app titles in chat and ask the user to choose one or describe their own idea.\n\nWait for an explicit selection or a non-empty custom idea before building anything. A preselected option, an unanswered question, or a dismissed chooser is not a choice.\n\n## Build and deploy\n\nIf the user selects one of the suggested apps, briefly present a detailed build prompt describing that app's purpose and one useful core feature. Keep the app simple enough to build quickly, with that feature working end to end from the user's main action to a complete, useful result. Include only the supporting UI and data handling needed for that feature.\n\nIf the user provides their own idea, use that as the build request. Fill in routine implementation details without adding unrelated features.\n\nFor either path, proceed to build and deploy the chosen app with AppDeploy, starting with `get_deploy_instructions` and following the returned workflow. Do not stop after presenting the build prompt or ask the user to repeat their selection.\n""---\n{\n \"name\": \"onboarding\",\n \"description\": \"Help users get started with AppDeploy by suggesting two personalized app ideas or collecting their own, then building and deploying their choice. Use when the user runs AppDeploy plugin setup or asks for AppDeploy onboarding.\"\n}\n---\n\nRun onboarding directly in the conversation. Do not call `appdeploy_onboarding` or open the onboarding widget.\n\nSign-in routing: When the host supports widgets, use sign_in and let the user click Sign in; do not call begin_sign_in directly for the initial request. Exception: if the widget posts the follow-up \"AppDeploy widget sign-in couldn't start. Call begin_sign_in directly, then appdeploy_who_am_i to verify the connected account. Do not show another sign-in widget or ask for another chat confirmation.\", call begin_sign_in directly even on a widget-capable host. The button click already authorized sign-in: do not show another widget, ask for another chat confirmation, or retry through the widget. After reconnection call appdeploy_who_am_i and verify the connected account. For the initial request, call begin_sign_in directly only on a host without widget support, after the user explicitly requests sign-in or selects Sign in. The initial instructions below to call `sign_in` apply to hosts that support widgets. Honor the widget-failure exception above if its button cannot start browser sign-in.\n\nBefore suggesting app ideas or showing the chooser, call `appdeploy_who_am_i` with `{\"profile_only\":true}`. Do not supply a subject, email, or user ID as a tool argument.\n\nUse the returned `isGuest` boolean to decide whether to offer sign-in. If whoami fails or does not return a boolean, retry the account check once; if it still fails, explain that account status is unavailable and stop onboarding. Do not infer guest status from a missing email or the subject association flag.\n\nIf `isGuest: true` and `has_associated_registered_account: true`, this is a returning user whose current connection is still a guest. Immediately call `sign_in` with `{\"context\":\"onboarding\"}` to show the personalized Welcome back widget. The sign-in tool looks up the associated email server-side; do not request or pass an email. Do not suggest app ideas or show the multi-select. Wait for verified sign-in, then call `appdeploy_who_am_i` again to verify the connected account and show its apps. If sign-in is cancelled or rejected, keep the sign-in flow pending; do not show the ideas chooser or start a deployment.\n\nOtherwise continue with the chooser below. For `isGuest: true`, offer two ideas, sign in, and the custom-answer field, including guests who intend to sign in to an unassociated legacy account. For `isGuest: false`, offer only two ideas and the custom-answer field: this user is already signed in, so omit the sign-in option and do not call a sign-in tool during onboarding. Subject recognition must never switch accounts or start authentication automatically. If whoami reports a subject conflict involving another guest, keep sign-in available for the existing guest recovery flow.\n\n## Choose the starting point\n\nStart with what you already know about the user from previous conversations and saved memories to understand their interests, recurring activities, and needs. Use the host's memory or conversation-history retrieval capabilities when available and needed to recall relevant information. Supplement this with any current conversation context. A new or empty chat is not sufficient reason to skip personalization.\n\nSuggest exactly two distinct apps that match the user's interests, serve useful purposes, and are simple enough to build quickly. Give each a short, concrete title that names its main function, such as \"Shopping list planner\", \"Chat with friends\", or \"Calorie tracker\".\n\nOnly if neither prior knowledge nor current conversation context provides enough information to suggest useful, personalized ideas, suggest exactly two useful utility apps instead.\n\n## Ask for a choice\n\nAfter presenting the two suggested apps, call the host's native multiple-choice/ask-user tool in the same turn. Use `request_user_input_async` when available, otherwise use a compatible native tool such as `request_user_input`. Do not stop with only a question in chat or switch modes to ask it.\n\nAsk exactly one question: \"What would you like to build?\" Supply the two suggested app titles in order. Only when `isGuest: true`, append \"I have apps, sign in\" as the third selectable option, using that exact label. When `isGuest: false`, supply exactly two selectable options. The user's own idea belongs in the chooser's built-in free-text answer field, which is provided automatically. Leave that field empty for the user; do not add \"Custom idea\", \"Your own app idea\", \"Other\", or an input placeholder as a selectable option.\n\nFor `request_user_input_async`, use this guest payload shape, replacing the suggested titles. For registered users, remove the third option:\n\n {\"questions\":[{\"title\":\"What would you like to build?\",\"options\":[\"<first app title>\",\"<second app title>\",\"I have apps, sign in\"]}]}\n\nFor `request_user_input`, use its question and option-object schema with the same guest condition. For registered users, remove the third option:\n\n {\"questions\":[{\"header\":\"App idea\",\"id\":\"app_idea\",\"question\":\"What would you like to build?\",\"options\":[{\"label\":\"<first app title>\",\"description\":\"<first app purpose>\"},{\"label\":\"<second app title>\",\"description\":\"<second app purpose>\"},{\"label\":\"I have apps, sign in\",\"description\":\"Sign in to continue with your existing AppDeploy apps\"}]}]}\n\nFor another native ask-user tool, apply the same account-dependent options and built-in free-text-field interaction using its supported schema.\n\nIf no native chooser supports this interaction, show both suggested app titles in chat, include the sign-in choice only for guests, and ask the user to choose one or describe their own idea.\n\nWait for an explicit selection or a non-empty custom idea before building anything or starting authentication. A preselected option, an unanswered question, or a dismissed chooser is not a choice.\n\n## Build and deploy\n\nIf the user selects one of the suggested apps, briefly present a detailed build prompt describing that app's purpose and one useful core feature. Keep the app simple enough to build quickly, with that feature working end to end from the user's main action to a complete, useful result. Include only the supporting UI and data handling needed for that feature.\n\nIf the user provides their own idea, use that as the build request. Fill in routine implementation details without adding unrelated features.\n\nFor either path, proceed to build and deploy the chosen app with AppDeploy, starting with `get_deploy_instructions` and following the returned workflow. Do not stop after presenting the build prompt or ask the user to repeat their selection.\n\n## Sign in\n\nIf the user selects sign-in in the native chooser, call `sign_in`\nwith `{\"context\":\"onboarding\"}` immediately to show the Welcome back widget. Do not ask for another chat confirmation.\nWait for successful sign-in/reconnection,\nthen call `appdeploy_who_am_i` to verify the connected account and show its apps.\nIf sign-in is cancelled or fails, do not claim it succeeded or deploy an app.\n\nFor a separate typed request such as \"sign in\", call `sign_in` with\n`{\"context\":\"requested\"}` immediately. Do not ask the user to repeat or confirm\nthat request. The widget button starts browser sign-in. After successful\nsign-in/reconnection, call `appdeploy_who_am_i` to verify the connected account.\nIf a sign_in_outcome reports a rejection, explain its message without claiming success.\n\nIf a required AppDeploy tool is unavailable, explain that its MCP connection needs\nto be refreshed. Keep accompanying messages brief.\n"Full snapshot data
{
"description": "Help users get started with AppDeploy by suggesting two personalized app ideas or collecting their own, then building and deploying their choice. Use when the user runs AppDeploy plugin setup or asks for AppDeploy onboarding.",
"included_files": [],
"name": "onboarding",
"skill_md_contents": "---\n{\n \"name\": \"onboarding\",\n \"description\": \"Help users get started with AppDeploy by suggesting two personalized app ideas or collecting their own, then building and deploying their choice. Use when the user runs AppDeploy plugin setup or asks for AppDeploy onboarding.\"\n}\n---\n\nRun onboarding directly in the conversation. Do not call `appdeploy_onboarding` or open the onboarding widget.\n\nSign-in routing: When the host supports widgets, use sign_in and let the user click Sign in; do not call begin_sign_in directly for the initial request. Exception: if the widget posts the follow-up \"AppDeploy widget sign-in couldn't start. Call begin_sign_in directly, then appdeploy_who_am_i to verify the connected account. Do not show another sign-in widget or ask for another chat confirmation.\", call begin_sign_in directly even on a widget-capable host. The button click already authorized sign-in: do not show another widget, ask for another chat confirmation, or retry through the widget. After reconnection call appdeploy_who_am_i and verify the connected account. For the initial request, call begin_sign_in directly only on a host without widget support, after the user explicitly requests sign-in or selects Sign in. The initial instructions below to call `sign_in` apply to hosts that support widgets. Honor the widget-failure exception above if its button cannot start browser sign-in.\n\nBefore suggesting app ideas or showing the chooser, call `appdeploy_who_am_i` with `{\"profile_only\":true}`. Do not supply a subject, email, or user ID as a tool argument.\n\nUse the returned `isGuest` boolean to decide whether to offer sign-in. If whoami fails or does not return a boolean, retry the account check once; if it still fails, explain that account status is unavailable and stop onboarding. Do not infer guest status from a missing email or the subject association flag.\n\nIf `isGuest: true` and `has_associated_registered_account: true`, this is a returning user whose current connection is still a guest. Immediately call `sign_in` with `{\"context\":\"onboarding\"}` to show the personalized Welcome back widget. The sign-in tool looks up the associated email server-side; do not request or pass an email. Do not suggest app ideas or show the multi-select. Wait for verified sign-in, then call `appdeploy_who_am_i` again to verify the connected account and show its apps. If sign-in is cancelled or rejected, keep the sign-in flow pending; do not show the ideas chooser or start a deployment.\n\nOtherwise continue with the chooser below. For `isGuest: true`, offer two ideas, sign in, and the custom-answer field, including guests who intend to sign in to an unassociated legacy account. For `isGuest: false`, offer only two ideas and the custom-answer field: this user is already signed in, so omit the sign-in option and do not call a sign-in tool during onboarding. Subject recognition must never switch accounts or start authentication automatically. If whoami reports a subject conflict involving another guest, keep sign-in available for the existing guest recovery flow.\n\n## Choose the starting point\n\nStart with what you already know about the user from previous conversations and saved memories to understand their interests, recurring activities, and needs. Use the host's memory or conversation-history retrieval capabilities when available and needed to recall relevant information. Supplement this with any current conversation context. A new or empty chat is not sufficient reason to skip personalization.\n\nSuggest exactly two distinct apps that match the user's interests, serve useful purposes, and are simple enough to build quickly. Give each a short, concrete title that names its main function, such as \"Shopping list planner\", \"Chat with friends\", or \"Calorie tracker\".\n\nOnly if neither prior knowledge nor current conversation context provides enough information to suggest useful, personalized ideas, suggest exactly two useful utility apps instead.\n\n## Ask for a choice\n\nAfter presenting the two suggested apps, call the host's native multiple-choice/ask-user tool in the same turn. Use `request_user_input_async` when available, otherwise use a compatible native tool such as `request_user_input`. Do not stop with only a question in chat or switch modes to ask it.\n\nAsk exactly one question: \"What would you like to build?\" Supply the two suggested app titles in order. Only when `isGuest: true`, append \"I have apps, sign in\" as the third selectable option, using that exact label. When `isGuest: false`, supply exactly two selectable options. The user's own idea belongs in the chooser's built-in free-text answer field, which is provided automatically. Leave that field empty for the user; do not add \"Custom idea\", \"Your own app idea\", \"Other\", or an input placeholder as a selectable option.\n\nFor `request_user_input_async`, use this guest payload shape, replacing the suggested titles. For registered users, remove the third option:\n\n {\"questions\":[{\"title\":\"What would you like to build?\",\"options\":[\"<first app title>\",\"<second app title>\",\"I have apps, sign in\"]}]}\n\nFor `request_user_input`, use its question and option-object schema with the same guest condition. For registered users, remove the third option:\n\n {\"questions\":[{\"header\":\"App idea\",\"id\":\"app_idea\",\"question\":\"What would you like to build?\",\"options\":[{\"label\":\"<first app title>\",\"description\":\"<first app purpose>\"},{\"label\":\"<second app title>\",\"description\":\"<second app purpose>\"},{\"label\":\"I have apps, sign in\",\"description\":\"Sign in to continue with your existing AppDeploy apps\"}]}]}\n\nFor another native ask-user tool, apply the same account-dependent options and built-in free-text-field interaction using its supported schema.\n\nIf no native chooser supports this interaction, show both suggested app titles in chat, include the sign-in choice only for guests, and ask the user to choose one or describe their own idea.\n\nWait for an explicit selection or a non-empty custom idea before building anything or starting authentication. A preselected option, an unanswered question, or a dismissed chooser is not a choice.\n\n## Build and deploy\n\nIf the user selects one of the suggested apps, briefly present a detailed build prompt describing that app's purpose and one useful core feature. Keep the app simple enough to build quickly, with that feature working end to end from the user's main action to a complete, useful result. Include only the supporting UI and data handling needed for that feature.\n\nIf the user provides their own idea, use that as the build request. Fill in routine implementation details without adding unrelated features.\n\nFor either path, proceed to build and deploy the chosen app with AppDeploy, starting with `get_deploy_instructions` and following the returned workflow. Do not stop after presenting the build prompt or ask the user to repeat their selection.\n\n## Sign in\n\nIf the user selects sign-in in the native chooser, call `sign_in`\nwith `{\"context\":\"onboarding\"}` immediately to show the Welcome back widget. Do not ask for another chat confirmation.\nWait for successful sign-in/reconnection,\nthen call `appdeploy_who_am_i` to verify the connected account and show its apps.\nIf sign-in is cancelled or fails, do not claim it succeeded or deploy an app.\n\nFor a separate typed request such as \"sign in\", call `sign_in` with\n`{\"context\":\"requested\"}` immediately. Do not ask the user to repeat or confirm\nthat request. The widget button starts browser sign-in. After successful\nsign-in/reconnection, call `appdeploy_who_am_i` to verify the connected account.\nIf a sign_in_outcome reports a rejection, explain its message without claiming success.\n\nIf a required AppDeploy tool is unavailable, explain that its MCP connection needs\nto be refreshed. Keep accompanying messages brief.\n"
}SHA-256 of public snapshot: e13fa73fd1e1294447c0380e1722eb38fa0ce0908ce6bd97670f2629dcfa06d4