setup12.3 KB
View saved version →
---
name: setup
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.
---
# 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,
keep their plan and continue with analysis setup. Create another plan only when
they ask for one.
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.
Once the user asks to create their plan, search the active exercise catalog for
valid exercise IDs and use `create_workout_plan` once for the complete multi-day
plan. Include practical sets, reps or durations and day labels. Check saved
workouts before retrying an uncertain create resp
Preview of the first 4,000 characters. Read full instructions →
training6.26 KB
View saved version →
---
name: training
description: Use Simple Muscle when the user wants to create or save a strength-training plan, open their training workspace, adapt a saved workout to their equipment, inspect exercise demonstrations, manage training preferences, review recorded workout progress, or enable and respond to workout analysis and automatic feedback.
---
# Simple Muscle training
Use the existing Simple Muscle connection and account authorization. Reuse goals,
equipment and preferences already supplied in the conversation. General fitness
explanations do not need account access or an installation pitch. Do not use the
plugin to diagnose injuries, prescribe treatment, track meals or buy equipment.
## Open and create plans
Use `open_training_dashboard` for saved workouts, first-plan setup, exercise browsing
and recent training. For Try it now, Set up, or a general get-started request,
follow the setup skill's guided onboarding before searching for exercises or
creating a plan. Open its onboarding form, point to it briefly, and wait. Do not
also ask the same questions in chat or open an inline questionnaire. Switch to
text only if the form is unavailable/unusable or the user prefers chat; reuse
any answers already submitted through the form. Collect the user's preferences;
do not turn a generic onboarding request into a preset beginner workout. Search the
active catalog for real exercise IDs before `create_workout_plan`; create a
complete multi-day plan once. Check saved workouts before retrying an uncertain
save so the user does not get duplicate plans.
Opening a workspace does not create a workout. A display tool requests a view;
do not claim the host visibly opened it unless confirmed. When a workspace is
already open, reuse it and let it refresh rather than opening duplicate widgets.
The existing `show_workout_overview` remains available when no workspace is open.
After a first-plan save, continue the setup skill's training-analysis step in
the same chat when the onboarding request includes activation. Do not stop at
the overview or app-download link. Verify subscriptions after host approval;
a saved plan alone does not mean Analyze or automatic feedback is active.
## Review workout edits
Use `open_workout_plan` to inspect a saved workout. An attached selection can name
one exercise or particular sets. Read `workspace_id`, `workout_id`,
`base_revision`, `selected_plan_id` and `selected_set_ids` from the workspace
context and stage only the requested changes with `propose_workout_edit`.
Update an existing draft with `update_workout_proposal` and its current version.
Let the user review the draft. Save through `apply_workout_proposal` only after
the user's explicit Save action. On a revision conflict, preserve the newer
saved workout and refresh before restaging. Discard only when requested.
Completed workout history is read-only; never claim to log or rewrite it here.
## Exercises and recorded progress
Use `search_workspace_exercises` to browse by name, equipment or muscle, and
`get_workspace_exercise` for workspace details and recent recorded sessions.
Use `show_exercise_info` for a demonstration/instructions request; pass
`exercise_id` when known or the natural name as `exercise_query` otherwise.
Use available catalog images/videos and instructions, without inventing media.
Use `show_training_stats` for recorded progress, frequency and volume. Use
`list_history`, `get_session` and `get_exercise_history` for additional detail.
Filter to the requested dates, workout or exercise; follow pagination and state
the covered history. Compare the user's own recorded sessions. Planned targets
are not completed sets or historical goal snapshots. State missing history
rather than inventing results. Discuss the findings in the current conversation;
keep plan changes separate until requested and reviewed.
## Preferences and gym tracking
Use `read_plugin_settings` and `update_plugin_settings` for explicitly requested
weight display
Preview of the first 4,000 characters. Read full instructions →