← Simple Muscle: Workout PlannerCONTENT HISTORY

Update to Simple Muscle: Workout Planner

Snapshot Oct 28, 2026 · 18:05 UTC · version 2.1.0

Collection source: downloaded plugin package.

WHAT CHANGED

Payment or plan references changed

Full description — Now says: Guide Simple Muscle onboarding when the user chooses Try it now, Set up, or asks to get started. Help them create their first plan and enable training...

Observed in published text. Live prices and checkout terms have not been verified by this change.

Save Simple Muscle: Workout Planner and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Full description

Before

Oct 24, 2026 · 13:09 UTC

Help a user create their first Simple Muscle workout plan when they choose Set up or ask to get started. Then optionally help them download and connect the iPhone app.

After

Oct 28, 2026 · 18:05 UTC

Guide Simple Muscle onboarding when the user chooses Try it now, Set up, or asks to get started. Help them create their first plan and enable training analysis. Also use for returning users who only need Analyze or workout feedback setup.

Skill instructions

Before

Oct 24, 2026 · 13:09 UTC

Help a user create their first Simple Muscle workout plan when they choose Set up or ask to get started. Then optionally help them download and connect the iPhone app. # Your first workout plan offer to open one with `open_workout_plan` ...

After

Oct 28, 2026 · 18:05 UTC

Guide Simple Muscle onboarding when the user chooses Try it now, Set up, or asks to get started. Help them create their first plan and enable training analysis. Also use for returning users who only need Analyze or workout feedback setup...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,18 +1,63 @@
 ---
 name: setup
-description: Help a user create their first Simple Muscle workout plan when they choose Set up or ask to get started. Then optionally help them download and connect the iPhone app.
+description: Guide Simple Muscle onboarding when the user chooses Try it now, Set up, or asks to get started. Help them create their first plan and enable training analysis. Also use for returning users who only need Analyze or workout feedback setup.
 ---
 
-# Your first workout plan
+# Set up Simple Muscle
+
+## Start guided onboarding
+
+Treat **Try it now**, **Set up**, "get started", and a request to use this setup
+skill as onboarding entry points. Start the flow here; do not replace it with a
+sample workout request or ask the user to copy another prompt. Briefly explain
+that you will help them set up their plan and training analysis, then open
+training home as described below.
+
+The starter request asks for guided onboarding and analysis activation together.
+Begin with the plan flow, then continue into analysis setup in this same chat.
+Do not assume beginner experience, dumbbells, a three-day schedule or 45-minute
+sessions. Read actual saved workouts and collect the user's own preferences.
+Defaults displayed by a form are not confirmed preferences until it is submitted.
+Clicking Try it now alone does not authorize creating a sample plan.
+
+If the user specifically asks only to enable analysis or feedback, or came from
+**Enable analysis** or **Set up Analyze**, go directly to **Enable training
+analysis** below. Do not collect training preferences or create a new plan for
+that request. If they already have a plan, keep it and continue with analysis
+setup.
+
+## Your first workout plan
 
 Open `open_training_dashboard` with empty arguments. If authentication is required,
 let the host complete the existing Simple Muscle connection, then continue.
 Read saved workouts before creating anything. If the user already has workouts,
-offer to open one with `open_workout_plan` or create a new plan; do not duplicate
-their existing plan automatically.
+keep their plan and continue with analysis setup. Create another plan only when
+they ask for one.
 
-For a first plan, use the onboarding form in training home when available. If
-the user supplies their preferences in chat, collect only missing details:
+For a first plan, prefer the extension form as the **only** questionnaire. After
+a successful dashboard request, reply briefly: "Fill in the first-plan form in
+the Simple Muscle panel, then submit it." Stop and wait. Do not also ask for the
+goal, experience, equipment, schedule or session length in chat, create an inline
+form, or call a question/elicitation tool. Do not start the analysis step while
+the user is still filling in their plan preferences.
+
+The opener's `onboarding.form_status: requested` is not render confirmation. The
+extension can publish `onboarding.form_rendered` and `submission_status` in model
+context after rendering and submission. A missing acknowledgement is not proof
+of failure; allow the user to use the form. Do not claim it visibly opened based
+only on a successful tool result. Form rendering and the ability to send a chat
+message are separate capabilities.
+
+Use text questions instead only when the opener reports an error, the user says
+the form is missing or unusable, or they explicitly prefer chat. Switch paths;
+do not keep both questionnaires going. If submission could not reach the chat,
+the form retains the answers and provides a prepared request. Tell the user to
+send it here. Reuse `submitted_preferences` from context or the submitted request
+and ask only for genuinely missing details, rather than starting onboarding over.
+Do not auto-create from a context update alone; wait for the submitted request or
+an explicit request to continue. For an unconfirmed send, check saved workouts
+before retrying creation. If the user supplies their preferences directly in
+chat, collect only missing details:
 their goal, available equipment, experience, days per week, and session length.
 Use answers already in the conversation. Ask about exercise preferences or
 movements they want to avoid only when useful; do not require that answer.
@@ -40,3 +85,114 @@
 `list_workouts` and `show_workout_overview` tools and explain that the workspace
 entrypoints are pending availability. Keep first-plan creation usable through
 the existing `create_workout_plan` tool.
+
+## Continue after the first plan is saved
+
+After saving the first plan, check the optional analysis setup using **Enable
+training analysis** below in this same chat. Do not stop at an App Store link
+without checking. If the current chat cannot connect analysis, complete the plan
+onboarding and use the short fallback below; optional analysis must not leave
+the user's entire onboarding marked incomplete. Do not wait for an iPhone
+installation before checking; account connection and approval are separate steps.
+
+The first-plan form and starter request explicitly ask to enable training
+analysis after saving. That request authorizes the subscription workflow: read
+status, request missing subscriptions through the host, and handle host approval.
+Do not ask a second optional-analysis question or make the user request setup
+again. If a user asked only for a plan without analysis, offer analysis once and
+continue after they accept. Respect an explicit decline and leave monitoring
+unchanged. Keep the saved plan if activation is pending, unavailable or declined.
+
+## Enable training analysis
+
+Call `get_analysis_status` on this plugin's connected account. If the tool is
+unavailable or `eventsEnabled` is not true, explain that analysis setup is not
+available on this connection and finish the rest of onboarding. Do not reconnect
+OAuth or repeatedly retry to obtain host capabilities.
+
+Interpret status correctly: `eventsEnabled` and `analyzeEnabled` describe the
+Simple Muscle server's feature availability. They do not prove ChatGPT plan
+eligibility, Work access, or monitoring support in this chat. `autoWorkoutAnalysis`
+is a saved preference, not an active connection. Only the connection fields
+confirm active monitoring; it may already be running in another chat.
+
+Reuse already active subscriptions before checking whether new setup is needed.
+If all requested monitoring is active, report it and point to its receiving chat;
+do not require this chat to support new subscriptions. For missing subscriptions,
+check whether this host actually exposes a subscription workflow. If it does
+not, go directly to **When this chat cannot connect analysis** below. Do not
+invent a subscription action or use the setup link as a substitute for one.
+
+Explain that Analyze sends a request from Simple Muscle and the findings appear
+in the AI chat where monitoring is enabled. Automatic feedback additionally
+responds after newly completed workouts sync. Use the same Simple Muscle account
+in ChatGPT and the app. For a first-plan request that includes analysis activation, continue directly
+with subscriptions after the plan is saved. An explicit request to enable
+Analyze already authorizes its setup; do not ask again. Only offer an opt-in
+when the user has not already requested analysis.
+
+Use the host's MCP Events workflow to subscribe to `analysis.requested` with
+empty arguments `{}` when `analyzeEnabled` is true. This covers History, workout
+and exercise requests. If `autoWorkoutAnalysis` is true, explain that automatic
+feedback is on and include `workout.completed` with empty arguments `{}` unless
+the user requests Analyze only. If the preference is false or the user asks for
+Analyze only, leave it unchanged and do not add completion monitoring. Tell them
+they can turn on automatic analysis in the app's AI Connections settings later.
+Do not request manual events when `analyzeEnabled` is false.
+
+Reuse existing monitors. If the requested subscriptions are already active,
+report their status and direct the user to their existing receiving chat; do not
+create another chat or monitor. When updating an existing monitor's behavior is
+requested, update its instructions in that chat. For partial setup, add only the
+missing subscriptions. The host supplies callback URLs and signing secrets and
+handles any approval; do not invent these or create a server-side substitute.
+
+Give the monitor these instructions: for each `analysis.requested` or
+`workout.completed` event, call `get_analysis_context` with `data.request_id`,
+follow `analysisBrief`, and reply with the complete readable analysis in the
+receiving chat. Compare the user's own recorded performance; state missing data
+and coverage. For automatic completions include the week overview. Invite
+follow-up questions. Never just return headings or an archive confirmation.
+Call `save_training_analysis` only if the user requests an archive. Keep saved
+plans and recorded history unchanged. Never send another analysis request in
+response to an event.
+
+After host approval, call `get_analysis_status` again. Confirm Analyze only when
+`analysisConnected` is true; confirm automatic analysis only when
+`autoWorkoutAnalysis` and `automaticConnected` are both true. Report partial or
+pending setup accurately. OAuth, sending a setup message, or opening a link does
+not prove activation. Tell the user to return to Simple Muscle to refresh status
+and use Analyze, and to continue the discussion in the receiving chat.
+
+## When this chat cannot connect analysis
+
+Use **Unavailable in this chat** for a requested connection the host cannot make.
+Use **Pending approval** only after a real supported subscription request is
+waiting for the user's approval. A setup message, preference, server flag or link
+does not establish pending approval. Report active parts separately in partial
+setup, and never switch off preferences or existing subscriptions as a fallback.
+
+Keep this explanation short and useful. If a plan was successfully saved, say it
+is ready; otherwise describe only the setup that actually completed. Explain that
+app-triggered Analyze and automatic workout feedback require a supported Work
+chat. If Work is unavailable to this user, they can skip this optional step. Do
+not infer their plan or an upgrade requirement from the status response.
+
+Offer direct review in the current chat when recorded-history tools are
+available: "You can still ask me here: Review my latest recorded workout."
+Direct chat review reads recorded history on request; it does not need background
+monitoring and does not activate the app's Analyze buttons. If those tools are
+also unavailable, do not promise this fallback. Keep plans and history unchanged.
+
+Do not show a Finish connecting button, repeatedly offer the same setup link,
+ask the user to return for another status check, or keep polling when the host
+lacks the action. Mention ChatGPT Work on web or Work with Cloud on desktop once
+as a conditional option, only if that access is available to them. Mobile
+onboarding support does not establish mobile monitoring support.
+
+In normal onboarding replies, use plain language: plan ready, not connected,
+unavailable in this chat, pending approval, or active. Do not expose event names,
+empty filters, tool calls, connection booleans or a technical diagnostic table
+unless the user explicitly asks for technical details. Do not label a preference
+or server feature flag as green/active analysis. Supported-host subscription
+instructions above are for the agent, not instructions to copy into the reply.
Full technical diff · 2 changed fields

changed /description

BEFORE
"Help a user create their first Simple Muscle workout plan when they choose Set up or ask to get started. Then optionally help them download and connect the iPhone app."
AFTER
"Guide Simple Muscle onboarding when the user chooses Try it now, Set up, or asks to get started. Help them create their first plan and enable training analysis. Also use for returning users who only need Analyze or workout feedback setup."

changed /skill_md_contents

BEFORE
"---\nname: setup\ndescription: Help a user create their first Simple Muscle workout plan when they choose Set up or ask to get started. Then optionally help them download and connect the iPhone app.\n---\n\n# Your first workout plan\n\nOpen `open_training_dashboard` with empty arguments. If authentication is required,\nlet the host complete the existing Simple Muscle connection, then continue.\nRead saved workouts before creating anything. If the user already has workouts,\noffer to open one with `open_workout_plan` or create a new plan; do not duplicate\ntheir existing plan automatically.\n\nFor a first plan, use the onboarding form in training home when available. If\nthe user supplies their preferences in chat, collect only missing details:\ntheir goal, available equipment, experience, days per week, and session length.\nUse answers already in the conversation. Ask about exercise preferences or\nmovements they want to avoid only when useful; do not require that answer.\n\nOnce the user asks to create their plan, search the active exercise catalog for\nvalid exercise IDs and use `create_workout_plan` once for the complete multi-day\nplan. Include practical sets, reps or durations and day labels. Check saved\nworkouts before retrying an uncertain create response to avoid duplicate plans.\nThe creation tool returns the saved plan and requests its overview. If training home is already open, let it refresh in place; do not open a duplicate view. Offer to open one saved workout with `open_workout_plan` if the user wants to inspect or edit it. Report success from the saved result, but do not claim that a panel opened unless the host confirms it.\n\nExplain that they can open a workout plan, select an exercise or sets, and ask\nfor a change. For editor requests containing workspace_id and base_revision,\nuse `propose_workout_edit`, or `update_workout_proposal` for an existing draft.\nStage only the requested changes and let the user review and save in the editor.\nCompleted sessions are read-only; never change recorded workout history.\n\nAfter the first plan is saved, explain: \"To track your progress in the gym,\ndownload the Simple Muscle app.\" Link to https://apps.apple.com/app/id6787905614\nand sign in with the same Simple Muscle account to sync the plan and log workouts.\nInstallation is not required\nto create or review the plan in ChatGPT. Use https://simplemuscle.ai/connect/chatgpt\nfor connection guidance and https://simplemuscle.ai/start for the web setup.\n\nIf the host has not made the new workspace tools available, use the existing\n`list_workouts` and `show_workout_overview` tools and explain that the workspace\nentrypoints are pending availability. Keep first-plan creation usable through\nthe existing `create_workout_plan` tool.\n"
AFTER
"---\nname: setup\ndescription: Guide Simple Muscle onboarding when the user chooses Try it now, Set up, or asks to get started. Help them create their first plan and enable training analysis. Also use for returning users who only need Analyze or workout feedback setup.\n---\n\n# Set up Simple Muscle\n\n## Start guided onboarding\n\nTreat **Try it now**, **Set up**, \"get started\", and a request to use this setup\nskill as onboarding entry points. Start the flow here; do not replace it with a\nsample workout request or ask the user to copy another prompt. Briefly explain\nthat you will help them set up their plan and training analysis, then open\ntraining home as described below.\n\nThe starter request asks for guided onboarding and analysis activation together.\nBegin with the plan flow, then continue into analysis setup in this same chat.\nDo not assume beginner experience, dumbbells, a three-day schedule or 45-minute\nsessions. Read actual saved workouts and collect the user's own preferences.\nDefaults displayed by a form are not confirmed preferences until it is submitted.\nClicking Try it now alone does not authorize creating a sample plan.\n\nIf the user specifically asks only to enable analysis or feedback, or came from\n**Enable analysis** or **Set up Analyze**, go directly to **Enable training\nanalysis** below. Do not collect training preferences or create a new plan for\nthat request. If they already have a plan, keep it and continue with analysis\nsetup.\n\n## Your first workout plan\n\nOpen `open_training_dashboard` with empty arguments. If authentication is required,\nlet the host complete the existing Simple Muscle connection, then continue.\nRead saved workouts before creating anything. If the user already has workouts,\nkeep their plan and continue with analysis setup. Create another plan only when\nthey ask for one.\n\nFor a first plan, prefer the extension form as the **only** questionnaire. After\na successful dashboard request, reply briefly: \"Fill in the first-plan form in\nthe Simple Muscle panel, then submit it.\" Stop and wait. Do not also ask for the\ngoal, experience, equipment, schedule or session length in chat, create an inline\nform, or call a question/elicitation tool. Do not start the analysis step while\nthe user is still filling in their plan preferences.\n\nThe opener's `onboarding.form_status: requested` is not render confirmation. The\nextension can publish `onboarding.form_rendered` and `submission_status` in model\ncontext after rendering and submission. A missing acknowledgement is not proof\nof failure; allow the user to use the form. Do not claim it visibly opened based\nonly on a successful tool result. Form rendering and the ability to send a chat\nmessage are separate capabilities.\n\nUse text questions instead only when the opener reports an error, the user says\nthe form is missing or unusable, or they explicitly prefer chat. Switch paths;\ndo not keep both questionnaires going. If submission could not reach the chat,\nthe form retains the answers and provides a prepared request. Tell the user to\nsend it here. Reuse `submitted_preferences` from context or the submitted request\nand ask only for genuinely missing details, rather than starting onboarding over.\nDo not auto-create from a context update alone; wait for the submitted request or\nan explicit request to continue. For an unconfirmed send, check saved workouts\nbefore retrying creation. If the user supplies their preferences directly in\nchat, collect only missing details:\ntheir goal, available equipment, experience, days per week, and session length.\nUse answers already in the conversation. Ask about exercise preferences or\nmovements they want to avoid only when useful; do not require that answer.\n\nOnce the user asks to create their plan, search the active exercise catalog for\nvalid exercise IDs and use `create_workout_plan` once for the complete multi-day\nplan. Include practical sets, reps or durations and day labels. Check saved\nworkouts before retrying an uncertain create response to avoid duplicate plans.\nThe creation tool returns the saved plan and requests its overview. If training home is already open, let it refresh in place; do not open a duplicate view. Offer to open one saved workout with `open_workout_plan` if the user wants to inspect or edit it. Report success from the saved result, but do not claim that a panel opened unless the host confirms it.\n\nExplain that they can open a workout plan, select an exercise or sets, and ask\nfor a change. For editor requests containing workspace_id and base_revision,\nuse `propose_workout_edit`, or `update_workout_proposal` for an existing draft.\nStage only the requested changes and let the user review and save in the editor.\nCompleted sessions are read-only; never change recorded workout history.\n\nAfter the first plan is saved, explain: \"To track your progress in the gym,\ndownload the Simple Muscle app.\" Link to https://apps.apple.com/app/id6787905614\nand sign in with the same Simple Muscle account to sync the plan and log workouts.\nInstallation is not required\nto create or review the plan in ChatGPT. Use https://simplemuscle.ai/connect/chatgpt\nfor connection guidance and https://simplemuscle.ai/start for the web setup.\n\nIf the host has not made the new workspace tools available, use the existing\n`list_workouts` and `show_workout_overview` tools and explain that the workspace\nentrypoints are pending availability. Keep first-plan creation usable through\nthe existing `create_workout_plan` tool.\n\n## Continue after the first plan is saved\n\nAfter saving the first plan, check the optional analysis setup using **Enable\ntraining analysis** below in this same chat. Do not stop at an App Store link\nwithout checking. If the current chat cannot connect analysis, complete the plan\nonboarding and use the short fallback below; optional analysis must not leave\nthe user's entire onboarding marked incomplete. Do not wait for an iPhone\ninstallation before checking; account connection and approval are separate steps.\n\nThe first-plan form and starter request explicitly ask to enable training\nanalysis after saving. That request authorizes the subscription workflow: read\nstatus, request missing subscriptions through the host, and handle host approval.\nDo not ask a second optional-analysis question or make the user request setup\nagain. If a user asked only for a plan without analysis, offer analysis once and\ncontinue after they accept. Respect an explicit decline and leave monitoring\nunchanged. Keep the saved plan if activation is pending, unavailable or declined.\n\n## Enable training analysis\n\nCall `get_analysis_status` on this plugin's connected account. If the tool is\nunavailable or `eventsEnabled` is not true, explain that analysis setup is not\navailable on this connection and finish the rest of onboarding. Do not reconnect\nOAuth or repeatedly retry to obtain host capabilities.\n\nInterpret status correctly: `eventsEnabled` and `analyzeEnabled` describe the\nSimple Muscle server's feature availability. They do not prove ChatGPT plan\neligibility, Work access, or monitoring support in this chat. `autoWorkoutAnalysis`\nis a saved preference, not an active connection. Only the connection fields\nconfirm active monitoring; it may already be running in another chat.\n\nReuse already active subscriptions before checking whether new setup is needed.\nIf all requested monitoring is active, report it and point to its receiving chat;\ndo not require this chat to support new subscriptions. For missing subscriptions,\ncheck whether this host actually exposes a subscription workflow. If it does\nnot, go directly to **When this chat cannot connect analysis** below. Do not\ninvent a subscription action or use the setup link as a substitute for one.\n\nExplain that Analyze sends a request from Simple Muscle and the findings appear\nin the AI chat where monitoring is enabled. Automatic feedback additionally\nresponds after newly completed workouts sync. Use the same Simple Muscle account\nin ChatGPT and the app. For a first-plan request that includes analysis activation, continue directly\nwith subscriptions after the plan is saved. An explicit request to enable\nAnalyze already authorizes its setup; do not ask again. Only offer an opt-in\nwhen the user has not already requested analysis.\n\nUse the host's MCP Events workflow to subscribe to `analysis.requested` with\nempty arguments `{}` when `analyzeEnabled` is true. This covers History, workout\nand exercise requests. If `autoWorkoutAnalysis` is true, explain that automatic\nfeedback is on and include `workout.completed` with empty arguments `{}` unless\nthe user requests Analyze only. If the preference is false or the user asks for\nAnalyze only, leave it unchanged and do not add completion monitoring. Tell them\nthey can turn on automatic analysis in the app's AI Connections settings later.\nDo not request manual events when `analyzeEnabled` is false.\n\nReuse existing monitors. If the requested subscriptions are already active,\nreport their status and direct the user to their existing receiving chat; do not\ncreate another chat or monitor. When updating an existing monitor's behavior is\nrequested, update its instructions in that chat. For partial setup, add only the\nmissing subscriptions. The host supplies callback URLs and signing secrets and\nhandles any approval; do not invent these or create a server-side substitute.\n\nGive the monitor these instructions: for each `analysis.requested` or\n`workout.completed` event, call `get_analysis_context` with `data.request_id`,\nfollow `analysisBrief`, and reply with the complete readable analysis in the\nreceiving chat. Compare the user's own recorded performance; state missing data\nand coverage. For automatic completions include the week overview. Invite\nfollow-up questions. Never just return headings or an archive confirmation.\nCall `save_training_analysis` only if the user requests an archive. Keep saved\nplans and recorded history unchanged. Never send another analysis request in\nresponse to an event.\n\nAfter host approval, call `get_analysis_status` again. Confirm Analyze only when\n`analysisConnected` is true; confirm automatic analysis only when\n`autoWorkoutAnalysis` and `automaticConnected` are both true. Report partial or\npending setup accurately. OAuth, sending a setup message, or opening a link does\nnot prove activation. Tell the user to return to Simple Muscle to refresh status\nand use Analyze, and to continue the discussion in the receiving chat.\n\n## When this chat cannot connect analysis\n\nUse **Unavailable in this chat** for a requested connection the host cannot make.\nUse **Pending approval** only after a real supported subscription request is\nwaiting for the user's approval. A setup message, preference, server flag or link\ndoes not establish pending approval. Report active parts separately in partial\nsetup, and never switch off preferences or existing subscriptions as a fallback.\n\nKeep this explanation short and useful. If a plan was successfully saved, say it\nis ready; otherwise describe only the setup that actually completed. Explain that\napp-triggered Analyze and automatic workout feedback require a supported Work\nchat. If Work is unavailable to this user, they can skip this optional step. Do\nnot infer their plan or an upgrade requirement from the status response.\n\nOffer direct review in the current chat when recorded-history tools are\navailable: \"You can still ask me here: Review my latest recorded workout.\"\nDirect chat review reads recorded history on request; it does not need background\nmonitoring and does not activate the app's Analyze buttons. If those tools are\nalso unavailable, do not promise this fallback. Keep plans and history unchanged.\n\nDo not show a Finish connecting button, repeatedly offer the same setup link,\nask the user to return for another status check, or keep polling when the host\nlacks the action. Mention ChatGPT Work on web or Work with Cloud on desktop once\nas a conditional option, only if that access is available to them. Mobile\nonboarding support does not establish mobile monitoring support.\n\nIn normal onboarding replies, use plain language: plan ready, not connected,\nunavailable in this chat, pending approval, or active. Do not expose event names,\nempty filters, tool calls, connection booleans or a technical diagnostic table\nunless the user explicitly asks for technical details. Do not label a preference\nor server feature flag as green/active analysis. Supported-host subscription\ninstructions above are for the agent, not instructions to copy into the reply.\n"
Full snapshot data
{
  "description": "Guide Simple Muscle onboarding when the user chooses Try it now, Set up, or asks to get started. Help them create their first plan and enable training analysis. Also use for returning users who only need Analyze or workout feedback setup.",
  "included_files": [],
  "name": "setup",
  "skill_md_contents": "---\nname: setup\ndescription: Guide Simple Muscle onboarding when the user chooses Try it now, Set up, or asks to get started. Help them create their first plan and enable training analysis. Also use for returning users who only need Analyze or workout feedback setup.\n---\n\n# Set up Simple Muscle\n\n## Start guided onboarding\n\nTreat **Try it now**, **Set up**, \"get started\", and a request to use this setup\nskill as onboarding entry points. Start the flow here; do not replace it with a\nsample workout request or ask the user to copy another prompt. Briefly explain\nthat you will help them set up their plan and training analysis, then open\ntraining home as described below.\n\nThe starter request asks for guided onboarding and analysis activation together.\nBegin with the plan flow, then continue into analysis setup in this same chat.\nDo not assume beginner experience, dumbbells, a three-day schedule or 45-minute\nsessions. Read actual saved workouts and collect the user's own preferences.\nDefaults displayed by a form are not confirmed preferences until it is submitted.\nClicking Try it now alone does not authorize creating a sample plan.\n\nIf the user specifically asks only to enable analysis or feedback, or came from\n**Enable analysis** or **Set up Analyze**, go directly to **Enable training\nanalysis** below. Do not collect training preferences or create a new plan for\nthat request. If they already have a plan, keep it and continue with analysis\nsetup.\n\n## Your first workout plan\n\nOpen `open_training_dashboard` with empty arguments. If authentication is required,\nlet the host complete the existing Simple Muscle connection, then continue.\nRead saved workouts before creating anything. If the user already has workouts,\nkeep their plan and continue with analysis setup. Create another plan only when\nthey ask for one.\n\nFor a first plan, prefer the extension form as the **only** questionnaire. After\na successful dashboard request, reply briefly: \"Fill in the first-plan form in\nthe Simple Muscle panel, then submit it.\" Stop and wait. Do not also ask for the\ngoal, experience, equipment, schedule or session length in chat, create an inline\nform, or call a question/elicitation tool. Do not start the analysis step while\nthe user is still filling in their plan preferences.\n\nThe opener's `onboarding.form_status: requested` is not render confirmation. The\nextension can publish `onboarding.form_rendered` and `submission_status` in model\ncontext after rendering and submission. A missing acknowledgement is not proof\nof failure; allow the user to use the form. Do not claim it visibly opened based\nonly on a successful tool result. Form rendering and the ability to send a chat\nmessage are separate capabilities.\n\nUse text questions instead only when the opener reports an error, the user says\nthe form is missing or unusable, or they explicitly prefer chat. Switch paths;\ndo not keep both questionnaires going. If submission could not reach the chat,\nthe form retains the answers and provides a prepared request. Tell the user to\nsend it here. Reuse `submitted_preferences` from context or the submitted request\nand ask only for genuinely missing details, rather than starting onboarding over.\nDo not auto-create from a context update alone; wait for the submitted request or\nan explicit request to continue. For an unconfirmed send, check saved workouts\nbefore retrying creation. If the user supplies their preferences directly in\nchat, collect only missing details:\ntheir goal, available equipment, experience, days per week, and session length.\nUse answers already in the conversation. Ask about exercise preferences or\nmovements they want to avoid only when useful; do not require that answer.\n\nOnce the user asks to create their plan, search the active exercise catalog for\nvalid exercise IDs and use `create_workout_plan` once for the complete multi-day\nplan. Include practical sets, reps or durations and day labels. Check saved\nworkouts before retrying an uncertain create response to avoid duplicate plans.\nThe creation tool returns the saved plan and requests its overview. If training home is already open, let it refresh in place; do not open a duplicate view. Offer to open one saved workout with `open_workout_plan` if the user wants to inspect or edit it. Report success from the saved result, but do not claim that a panel opened unless the host confirms it.\n\nExplain that they can open a workout plan, select an exercise or sets, and ask\nfor a change. For editor requests containing workspace_id and base_revision,\nuse `propose_workout_edit`, or `update_workout_proposal` for an existing draft.\nStage only the requested changes and let the user review and save in the editor.\nCompleted sessions are read-only; never change recorded workout history.\n\nAfter the first plan is saved, explain: \"To track your progress in the gym,\ndownload the Simple Muscle app.\" Link to https://apps.apple.com/app/id6787905614\nand sign in with the same Simple Muscle account to sync the plan and log workouts.\nInstallation is not required\nto create or review the plan in ChatGPT. Use https://simplemuscle.ai/connect/chatgpt\nfor connection guidance and https://simplemuscle.ai/start for the web setup.\n\nIf the host has not made the new workspace tools available, use the existing\n`list_workouts` and `show_workout_overview` tools and explain that the workspace\nentrypoints are pending availability. Keep first-plan creation usable through\nthe existing `create_workout_plan` tool.\n\n## Continue after the first plan is saved\n\nAfter saving the first plan, check the optional analysis setup using **Enable\ntraining analysis** below in this same chat. Do not stop at an App Store link\nwithout checking. If the current chat cannot connect analysis, complete the plan\nonboarding and use the short fallback below; optional analysis must not leave\nthe user's entire onboarding marked incomplete. Do not wait for an iPhone\ninstallation before checking; account connection and approval are separate steps.\n\nThe first-plan form and starter request explicitly ask to enable training\nanalysis after saving. That request authorizes the subscription workflow: read\nstatus, request missing subscriptions through the host, and handle host approval.\nDo not ask a second optional-analysis question or make the user request setup\nagain. If a user asked only for a plan without analysis, offer analysis once and\ncontinue after they accept. Respect an explicit decline and leave monitoring\nunchanged. Keep the saved plan if activation is pending, unavailable or declined.\n\n## Enable training analysis\n\nCall `get_analysis_status` on this plugin's connected account. If the tool is\nunavailable or `eventsEnabled` is not true, explain that analysis setup is not\navailable on this connection and finish the rest of onboarding. Do not reconnect\nOAuth or repeatedly retry to obtain host capabilities.\n\nInterpret status correctly: `eventsEnabled` and `analyzeEnabled` describe the\nSimple Muscle server's feature availability. They do not prove ChatGPT plan\neligibility, Work access, or monitoring support in this chat. `autoWorkoutAnalysis`\nis a saved preference, not an active connection. Only the connection fields\nconfirm active monitoring; it may already be running in another chat.\n\nReuse already active subscriptions before checking whether new setup is needed.\nIf all requested monitoring is active, report it and point to its receiving chat;\ndo not require this chat to support new subscriptions. For missing subscriptions,\ncheck whether this host actually exposes a subscription workflow. If it does\nnot, go directly to **When this chat cannot connect analysis** below. Do not\ninvent a subscription action or use the setup link as a substitute for one.\n\nExplain that Analyze sends a request from Simple Muscle and the findings appear\nin the AI chat where monitoring is enabled. Automatic feedback additionally\nresponds after newly completed workouts sync. Use the same Simple Muscle account\nin ChatGPT and the app. For a first-plan request that includes analysis activation, continue directly\nwith subscriptions after the plan is saved. An explicit request to enable\nAnalyze already authorizes its setup; do not ask again. Only offer an opt-in\nwhen the user has not already requested analysis.\n\nUse the host's MCP Events workflow to subscribe to `analysis.requested` with\nempty arguments `{}` when `analyzeEnabled` is true. This covers History, workout\nand exercise requests. If `autoWorkoutAnalysis` is true, explain that automatic\nfeedback is on and include `workout.completed` with empty arguments `{}` unless\nthe user requests Analyze only. If the preference is false or the user asks for\nAnalyze only, leave it unchanged and do not add completion monitoring. Tell them\nthey can turn on automatic analysis in the app's AI Connections settings later.\nDo not request manual events when `analyzeEnabled` is false.\n\nReuse existing monitors. If the requested subscriptions are already active,\nreport their status and direct the user to their existing receiving chat; do not\ncreate another chat or monitor. When updating an existing monitor's behavior is\nrequested, update its instructions in that chat. For partial setup, add only the\nmissing subscriptions. The host supplies callback URLs and signing secrets and\nhandles any approval; do not invent these or create a server-side substitute.\n\nGive the monitor these instructions: for each `analysis.requested` or\n`workout.completed` event, call `get_analysis_context` with `data.request_id`,\nfollow `analysisBrief`, and reply with the complete readable analysis in the\nreceiving chat. Compare the user's own recorded performance; state missing data\nand coverage. For automatic completions include the week overview. Invite\nfollow-up questions. Never just return headings or an archive confirmation.\nCall `save_training_analysis` only if the user requests an archive. Keep saved\nplans and recorded history unchanged. Never send another analysis request in\nresponse to an event.\n\nAfter host approval, call `get_analysis_status` again. Confirm Analyze only when\n`analysisConnected` is true; confirm automatic analysis only when\n`autoWorkoutAnalysis` and `automaticConnected` are both true. Report partial or\npending setup accurately. OAuth, sending a setup message, or opening a link does\nnot prove activation. Tell the user to return to Simple Muscle to refresh status\nand use Analyze, and to continue the discussion in the receiving chat.\n\n## When this chat cannot connect analysis\n\nUse **Unavailable in this chat** for a requested connection the host cannot make.\nUse **Pending approval** only after a real supported subscription request is\nwaiting for the user's approval. A setup message, preference, server flag or link\ndoes not establish pending approval. Report active parts separately in partial\nsetup, and never switch off preferences or existing subscriptions as a fallback.\n\nKeep this explanation short and useful. If a plan was successfully saved, say it\nis ready; otherwise describe only the setup that actually completed. Explain that\napp-triggered Analyze and automatic workout feedback require a supported Work\nchat. If Work is unavailable to this user, they can skip this optional step. Do\nnot infer their plan or an upgrade requirement from the status response.\n\nOffer direct review in the current chat when recorded-history tools are\navailable: \"You can still ask me here: Review my latest recorded workout.\"\nDirect chat review reads recorded history on request; it does not need background\nmonitoring and does not activate the app's Analyze buttons. If those tools are\nalso unavailable, do not promise this fallback. Keep plans and history unchanged.\n\nDo not show a Finish connecting button, repeatedly offer the same setup link,\nask the user to return for another status check, or keep polling when the host\nlacks the action. Mention ChatGPT Work on web or Work with Cloud on desktop once\nas a conditional option, only if that access is available to them. Mobile\nonboarding support does not establish mobile monitoring support.\n\nIn normal onboarding replies, use plain language: plan ready, not connected,\nunavailable in this chat, pending approval, or active. Do not expose event names,\nempty filters, tool calls, connection booleans or a technical diagnostic table\nunless the user explicitly asks for technical details. Do not label a preference\nor server feature flag as green/active analysis. Supported-host subscription\ninstructions above are for the agent, not instructions to copy into the reply.\n"
}

SHA-256 of public snapshot: 2c408232465f7bea47952f3d6df8438b120597eaeb571bd0106cd2c8312f4276