← LifterlyCONTENT HISTORY

Update to Lifterly

Snapshot Nov 4, 2026 · 12:10 UTC · version 1.0.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Lifterly and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Build one strength-training session in Lifterly from the user's real profile, equipment, history and results, show it, and add it to their plan once they agree. Use when the user asks for a workout, a session for today or a given day, or a session targeting given muscles or a split part.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 359
    },
    {
      "relative_path": "references/programming.md",
      "size_in_bytes": 2869
    }
  ],
  "name": "build-workout",
  "skill_md_contents": "---\nname: build-workout\ndescription: Build one strength-training session in Lifterly from the user's real profile, equipment, history and results, show it, and add it to their plan once they agree. Use when the user asks for a workout, a session for today or a given day, or a session targeting given muscles or a split part.\n---\n\n# Build a workout\n\nFollow the user's explicit instructions first; this workflow fills in what they\ndid not specify.\n\n## Gather\n\n1. `get_training_profile` for goal, level, equipment, weekly goal and weight\n   unit. If the user has no profile, say so and ask about their goal and\n   equipment instead of guessing.\n2. `list_workouts` (last two weeks) to see what they trained recently.\n3. Decide the workout type and split part: from the user's words, otherwise\n   the next part in their usual rotation, otherwise `fullBody`.\n4. `search_exercises` with that `workoutType` and `splitPart`.\n5. `get_exercise_progress` for the exercises you are considering, to set\n   weights from their results.\n\nAsk one short question instead of guessing when the day, the time available or\nthe muscles to train are unclear and matter.\n\n## Build\n\nApply [references/programming.md](references/programming.md): exercise choice,\nsets, weights in kg, rest in seconds, session length.\n\n## Show and confirm\n\n1. Call `show_workout_proposal` with the complete plan (the same input\n   `create_planned_workout` takes). It shows the session with an\n   \"Add to my plan\" button; nothing is saved yet.\n2. Explain the choice in two or three sentences, weights in the user's unit.\n3. If the user asks for changes, adjust and show the proposal again.\n4. When they agree in the conversation, call `create_planned_workout` with the\n   same plan (unless they already added it with the button: the tool result\n   says so), then `show_planned_workout` with its id.\n\n## Do not\n\n- Invent exercise ids or results.\n- Save anything before the user agrees.\n- Plan through injuries the user mentioned; leave the affected exercises out\n  and suggest `ban_exercises` if the limitation is lasting.\n"
}

SHA-256 of public snapshot: a9b0519db9650126b9c6b6952cbb0dfd929e604dc76161ad0cf20a3e1b0b7449