{"id":48266,"plugin_id":"plugin_asdk_app_6a4d07cf0b208191bbb509c02fb72ee2","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:35:53.841Z","digest":"bc79c501b20efda078e9e9ac3c8f35ad4e795726fac047ead141cbb9d0c35246","against":null,"payload":{"description":"Turn a supplied recipe, meal-prep plan, or food goal into a sequenced cook-along checklist and invoke display-guide. Use for step-by-step cooking instructions, mise en place, serving-size adaptations, coordinated dishes, observable doneness checks, and safe serving or storage guidance. Do not use for restaurant or grocery recommendations, nutrition or medical-diet advice, suspected food-poisoning assessment, recipe discovery without an actionable cooking guide, or improvised home-canning and fermentation protocols.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":236}],"name":"cook-along-guide","skill_md_contents":"---\nname: cook-along-guide\ndescription: >-\n  Turn a supplied recipe, meal-prep plan, or food goal into a sequenced cook-along checklist and invoke display-guide. Use for step-by-step cooking instructions, mise en place, serving-size adaptations, coordinated dishes, observable doneness checks, and safe serving or storage guidance. Do not use for restaurant or grocery recommendations, nutrition or medical-diet advice, suspected food-poisoning assessment, recipe discovery without an actionable cooking guide, or improvised home-canning and fermentation protocols.\n---\n\n# Cook-Along Guide\n\nCreate a practical guide that a cook can follow without repeatedly rereading the source. Prefer a simple, safe sequence over culinary exposition, then present it with `display-guide`.\n\n## Build the cooking plan\n\n1. Establish the source and constraints.\n   - Treat a supplied recipe as the source of truth unless the user requests an adaptation.\n   - For a food goal, choose a straightforward preparation that fits the stated meal, time, ingredients, and skill level. Distinguish user-provided facts from assumptions.\n   - Determine the target servings, dietary restrictions or allergies, available equipment, and any timing constraint that materially changes the plan.\n   - Ask one concise question when a missing answer affects safety or feasibility. Otherwise, use a conservative, clearly stated assumption.\n2. Normalize quantities and equipment.\n   - Set one target yield and apply the same scaling factor to every scalable ingredient.\n   - Keep one authoritative total quantity for each ingredient. Mark it as divided when separate steps use portions, and specify each portion at its point of use.\n   - Use consistent units and practical precision. Do not round amounts in ways that materially change baking ratios, seasoning concentration, or food safety.\n   - Do not scale oven temperature, cooking time, pan size, or appliance capacity mechanically. Adjust them only when the changed batch requires it, and state the adjustment.\n   - Check that vessels and appliances can hold the batch safely; split batches when crowding would undermine cooking or exceed capacity.\n3. Design the sequence.\n   - Move washing, measuring, chopping, marinating, thawing, preheating, and equipment setup into preparation when they should happen before active cooking.\n   - Order instructions by dependency. Start long passive tasks first and use their waiting periods for independent prep.\n   - For multiple dishes, work backward from the serving time and place each action in one integrated sequence.\n   - Make each instruction atomic and imperative. Include the vessel or tool, heat level or setting, approximate duration, and an observable endpoint when relevant.\n   - Pair time estimates with sensory or measured cues; never rely on \"cook until done\" alone.\n\n## Apply safety guardrails\n\n- Treat an allergy as a safety constraint, not a preference. Clarify an ambiguous allergen before proceeding.\n- Never claim that a dish, substitution, packaged ingredient, or kitchen is allergen-free. Tell the user to verify every label and account for shared tools, surfaces, oil, and other cross-contact risks.\n- Preserve relevant handwashing, raw-versus-ready-to-eat separation, clean-tool, thawing, and storage steps. Do not recommend tasting mixtures that may be unsafe while raw.\n- Use a food thermometer when safe doneness depends on internal temperature, and give both the measurement location and a non-temperature quality cue when useful.\n- Verify exact safety-critical temperatures, holding limits, cooling times, and storage windows against current guidance from an authoritative government food-safety or public-health source. Prefer the user's jurisdiction when known. Do not guess when verification is unavailable.\n- If a supplied recipe conflicts with current authoritative safety guidance, do not silently repeat the unsafe direction. Use the safer requirement and explain the change briefly.\n- Do not improvise hazardous preservation processes or advise on whether symptoms after eating require treatment. Direct those cases to the appropriate validated process or health authority.\n\n## Map the plan to `display-guide`\n\nUse only the supported fields and omit empty optional sections:\n\n- `requirements`: List ingredients with exact total quantities, noting divided uses, followed by essential equipment. Keep the target yield consistent with these amounts.\n- `preparation`: List mise en place, safe setup, preheating, and advance prep in the order needed.\n- `instructions`: Provide at least one dependency-ordered cooking action. Keep required safety actions here rather than hiding them in tips.\n- `wrapUp`: Include finishing, resting, serving, prompt cooling or storage, and task-specific cleanup when relevant.\n- `tips`: Add only optional substitutions, coordination advice, or troubleshooting that is not required for success or safety.\n- `notes`: State the yield, material assumptions or adaptations, and concise allergy or safety caveats that apply to the whole guide.\n- `reason`: Briefly state that the tool is presenting a cook-along guide.\n\nDo not add titles, timing objects, citations, nested steps, or other unsupported fields. Put source citations in the surrounding response when external verification was needed.\n\n## Check and present\n\nBefore calling the tool, verify that:\n\n- Every ingredient used in an instruction appears in `requirements`, and every listed ingredient is used or intentionally reserved for serving.\n- Quantities, servings, pan capacity, temperatures, and units agree throughout.\n- Preparation completes the mise en place needed before each time-sensitive step.\n- Instructions have no dependency inversions, unexplained simultaneous actions, vague endpoints, or duplicated work.\n- Required allergy and food-safety controls are explicit, current, and not relegated to optional tips.\n- `instructions` is non-empty and every checklist item is a concise, standalone action.\n\nInvoke `display-guide` once with the completed guide. Keep the accompanying prose brief and use it only for necessary source attribution or a limitation that does not fit the guide.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}