Update to Liftory

{
  "description": "Put together a new nutrition plan (a menu of meals, options, and foods) in Liftory for the signed-in user or for a client they coach, from the targets and preferences the user gives, from saved meals, or from a template; change an existing menu; and keep the meal library. Use when the user asks to create, set up, write, or change a menu or nutrition plan, or to save, file, or delete a meal. Not for copying a menu from a document or picture.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 262
    },
    {
      "relative_path": "references/menu-model.md",
      "size_in_bytes": 3469
    }
  ],
  "name": "build-nutrition-plan",
  "skill_md_contents": "---\nname: build-nutrition-plan\ndescription: Put together a new nutrition plan (a menu of meals, options, and foods) in Liftory for the signed-in user or for a client they coach, from the targets and preferences the user gives, from saved meals, or from a template; change an existing menu; and keep the meal library. Use when the user asks to create, set up, write, or change a menu or nutrition plan, or to save, file, or delete a meal. Not for copying a menu from a document or picture.\n---\n# Build a nutrition plan\n\nThe user's explicit instructions take priority over this skill. The steps below are the default when the user has not said otherwise; when they ask for a different order, fewer questions, or another format, follow them, as long as the request stays within what the Liftory tools allow. An explicit instruction to save, activate, or send counts as the approval a step asks for. Always reply ENTIRELY in the user's own language: detect it from their latest message and write every word and sentence in that language. Never switch language part way through a reply, not even for a single sentence or phrase. Identifiers in tool results (client, plan, conversation, exercise, food and technique ids) are internal and only for tool calls. Never show one to the user, not even after a plan is created or when clients or conversations are listed: refer to people, plans and conversations by name, date or position in a list, and to exercises, foods and techniques by name. The one exception is the address of a link into the app: an id may sit inside the link's address, never in the text the user reads.\n\nLiftory gives general fitness guidance, not medical or dietary advice. Health information is never asked for:\n- Never ask about medical conditions, pain, injuries, pregnancy, eating disorders, medication, or body measurements, and never make one of them a question in a step.\n- When the user brings one up on their own, give only general information, recommend a qualified professional for anything that depends on it, and do not ask follow-up questions about it. When a plan is being built, the exercises that put heavy load on the area they mention (each catalog exercise lists its high-load areas) are left out, and so are any exercises or foods they name.\n- Do not store it: never write it into a plan, a menu, or a rationale, and do not repeat it back in later replies.\n- Leave out every exercise or food the user asks to leave out. The reason is not needed and is not recorded.\n\n## Whose menu\n\nEvery tool acts as the signed-in Liftory user. Decide whose data the request is about before reading or writing anything:\n- The user's own data: call the tools without clientId.\n- A client the user coaches: call list_clients, find the client by the name the user gave, and give that client's clientId. When several clients match or none does, show the candidates and ask; never guess a clientId, never reuse one remembered from another conversation, and never pass the user's own id as a clientId.\n- Unclear whether it is for the user or a client: call whoami, which says whether the user coaches clients, and ask only when they do.\n- list_clients is empty: the user coaches no one, so only their own data is reachable. Say so instead of looking for the person another way.\n\n## Steps\n\n1. Decide whose menu it is, as above. Call get_last_nutrition_plan for that person when the user refers to their current menu, so the new one can build on it. When the user wants to start from a template, call list_nutrition_plans with templates true and get_nutrition_plan for the one they pick; its menu is the starting draft, saved with isTemplate false.\n2. Collect what the menu needs and ask for what is missing, in one message: the daily targets (or that there are none), the number of meals and their times, the foods they want included or left out, and whether some days differ. Do not set calorie or macro targets yourself; use the ones the user gives.\n3. When the user wants their saved meals, call list_meals (with library or query when they name one) and use the meals they pick exactly as list_meals returns them, mealId included. Find every other food with search_food, in the user's language and with their language code as the locale. Use only foods it returns, with their foodId. When nothing suitable comes back, say so, and keep the line without a foodId only if the user agrees.\n4. Build the draft as [references/menu-model.md](references/menu-model.md) describes and call validate_nutrition_plan. Fix every unknown foodId and every problem it reports, and validate again until both are empty.\n5. Show the menu: each meal with its options and foods with amounts, the targets, the weekly limits and notes, the rationale (the goal as the user said it, and the reasoning behind the targets), and the warnings validation returned. Ask the user to approve it, and ask whether it should replace the menu being followed now (which archives the person's other menus) or be saved without activating it.\n6. After approval, call create_nutrition_plan with the same draft, clientId when it is for a client, and activate as the user chose.\n7. Confirm the menu name, whose account it is on, and whether it is active. To activate a menu saved earlier, call activate_nutrition_plan with its planId only after the user asks for it.\n\n## Changing an existing menu\n\nWhen the user asks to change a menu that already exists, change it in place rather than creating a second one: update_nutrition_plan rewrites it and keeps the days already logged against it. Read it with get_nutrition_plan (or get_last_nutrition_plan), make only the changes asked for, and keep every other name as it is. Show what changes, ask for approval, and call update_nutrition_plan with the planId, the whole changed menu, and clientId for a client. When only the notes change, use update_nutrition_rules instead.\n\n## The meal library\n\n- list_meals shows the signed-in user's meals with their figures; a meal marked fromCoach was shared by their coach and cannot be changed.\n- To save a meal, call save_meal with the meal in the option shape, after the user approves it; without mealId it is a new meal, which is also how a fromCoach meal is copied to make it editable. With a mealId it replaces that meal; a mealId and library alone files it under other libraries.\n- Call delete_meal only for the meal the user asked to delete.\n\n## Rules\n\nNever invent facts:\n- Every id (clientId, planId, exerciseId, techniqueId, foodId, sessionId) comes from a tool result in this conversation, never from memory or a guess.\n- Clients, exercises, techniques, and foods are named only as a tool returned them or as the user wrote them.\n- Numbers (sets, reps, durations, rest, loads, amounts, calorie and macro targets) come from the user, from their document, or from a design you showed them and they approved. Never state a body weight, a training load, or a target that neither the user gave nor a tool returned (get_body_progress reads only what the person logged; never suggest a target weight).\n- When a fact you need is missing, ask for it instead of assuming it.\n\nWrites change a real Liftory account that a coach or client relies on:\n- Before any tool that saves, activates, or sends, show the user exactly what will be written and for whom (themselves, or the client by name), and call the tool only after they approve it in this conversation. One approval covers one write.\n- Never delete a plan, a menu, or a message, and never ask the user to delete the old version to make room for a new one. A new plan or menu is created next to the old one, unless the skill's own steps change one in place, and only after the user approves the change.\n- A meal is removed from the meal library only when the user asks for that meal to be deleted.\n- When a write answers with unknown ids or problems, nothing was saved: fix what it names, show the user what changed, and ask again before the next attempt.\n\nWhen a tool fails or returns nothing:\n- \"You are not this person's trainer, or their coaching access has ended.\": stop working on that person and tell the user in plain words. Do not retry with another id or as the user's own data.\n- \"Your Liftory connection was revoked or has expired.\": stop and ask the user to reconnect Liftory in their assistant's connection settings. Do not retry until they have.\n- A null or empty result means there is nothing there: say so plainly. Never fill the gap with content of your own.\n- Any other error: tell the user what Liftory answered, in plain words, and ask how to continue.\n\n## Output\n\nThe menu is shown meal by meal as a list, with amounts as they will be stored. Nothing is described as saved until create_nutrition_plan has returned a planId.\n\nAfter a write succeeds, end the confirmation with one markdown link to where it can be seen, its text naming the place and the id only inside the address, filled from the tool result:\n- A training plan for themselves: [the plan](https://liftory.ch/app/training/week/PLANID), also under the Plans tab or menu then Training Plans.\n- A training plan for a client: [the plan](https://liftory.ch/app/admin/training-editor/edit/PLANID?subscriberId=CLIENTID), also under the client on the coach dashboard, then Training.\n- A nutrition plan for themselves: [your nutrition day](https://liftory.ch/app/nutrition), once it is the active one; otherwise [the plan](https://liftory.ch/app/admin/nutrition-editor/edit/PLANID).\n- A nutrition plan for a client: [the plan](https://liftory.ch/app/admin/nutrition-editor/edit/PLANID?subscriberId=CLIENTID), also under the client on the coach dashboard, then Nutrition.\n- A message: [the conversation](https://liftory.ch/app/messages).\nThe link opens the app on a phone where it is installed, and the browser elsewhere.\n"
}