Update to Qook

{
  "description": "Find everyday recipe ideas, adapt an individual recipe to pantry ingredients or preferences, and locate verified recipe videos with Qook and host capabilities. Use for a dish or recipe choice rather than a weekly menu, a shopping-only task, or adding courses to an unchanged main.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 226
    }
  ],
  "name": "qook-recipes",
  "skill_md_contents": "---\nname: qook-recipes\ndescription: Find everyday recipe ideas, adapt an individual recipe to pantry ingredients or preferences, and locate verified recipe videos with Qook and host capabilities. Use for a dish or recipe choice rather than a weekly menu, a shopping-only task, or adding courses to an unchanged main.\n---\n\n# Qook recipes\n\nHelp the user choose or adapt a practical dish. Use the latest servings, dietary choices, allergies, dislikes, equipment, budget and available time supplied in this conversation. Honor detailed restrictions and special instructions; clarify conflicts rather than dropping them. This release uses guest preferences from the chat, with no account loading or synchronization. Ask only a missing detail that changes the result. A request for one dinner should stay one dinner, not become a week or a full onboarding form.\n\n## Recipe ideas and adaptations\n\nCall `get_planning_guidance_v2` with current preferences, then draft the recipe in the host assistant. Qook displays and validates supplied recipes; it does not search a private recipe database or call another generation model. For ordinary recipe ideas, do not imply the result came from a published source. If the user asks for an existing published recipe, use available host browsing, verify the actual page, and identify the source and any adaptations. If browsing is unavailable, offer an original recipe or a search phrase, without inventing a source.\n\nUse `render_meal_plan_v2` to display the recipe in the smallest matching scope: one day and the requested meal slot for a single dish. Include meal name, servings, positive ingredient quantities with explicit units, useful nonempty instructions, and cooking time when known. Ingredient quantities cover the entire recipe at the listed servings, not each person. When offering several ideas, briefly let the user choose before turning them into a menu unless they asked for full recipes for every option.\n\nFor substitutions, preserve the requested dish and change only the necessary ingredients and steps. Check alternatives against all exclusions, not only the newest preference. Retain ingredient forms, recalculate amounts when servings actually change, and account for soaking/fermentation within the deadline. Missing time is a reason to offer a feasible alternative, not to promise impossible preparation. After an edit to an existing plan, re-render the complete revised plan and preserve unaffected recipes. Resolve returned warnings; structure validation does not prove culinary suitability or allergen safety.\n\nInclude approximate per-serving nutrition by default and retain an explicit `includeNutrition:false`. Accept user goals such as weight management as ordinary free-text preferences; they do not need to become clinical plans or diagnoses. Tailor practical portions and recipe choices without promises of treatment, exact nutrients, guaranteed weight change or allergy safety. Make label/cross-contact checks relevant to the stated allergy rather than repeating a generic disclaimer on every card.\n\n## Videos and photos\n\nFor a recipe-video request, use available host browsing to verify an existing relevant video and its actual title/link. Point out material ingredient or method differences from the selected recipe. With no browsing, provide a useful search phrase; do not invent a YouTube URL or claim a video was fetched/generated by Qook. A user asking for a video does not request a new meal plan.\n\nFor a supplied fridge/pantry photo, use host vision if available to list visible ingredients and uncertain items for confirmation. Do not infer hidden stock, freshness or safety. Qook has no photo-upload/recognition endpoint.\n\nMeal photos and meal-image requests are currently off in Qook. Do not offer image controls, add `imageUrl` to new plans or claim a weekly image board was generated. Offer the recipe text, weekly calendar or Qook-branded meal/day/week text-card downloads instead.\n\nFor a grocery checklist after the recipe, use [Qook groceries](../qook-groceries/SKILL.md). For an optional side or drink that leaves the main recipe intact, use [Qook's Magic](../qook-magic/SKILL.md); do not silently add extra courses during recipe adaptation.\n"
}