Update to Pantry Persona

{
  "description": "Takes a quick look around the kitchen and returns a short list of suggested fixes: food expiring soon, dinners not yet planned for the next three days, and staples missing from the shopping list. Changes nothing until the user approves. Use when the user says \"check my kitchen\", \"daily kitchen check\", \"anything I should know\", or \"what needs attention\". Not for full weekly planning or logging a receipt.",
  "included_files": [],
  "name": "kitchen-check",
  "skill_md_contents": "---\nname: kitchen-check\ndescription: Takes a quick look around the kitchen and returns a short list of suggested fixes: food expiring soon, dinners not yet planned for the next three days, and staples missing from the shopping list. Changes nothing until the user approves. Use when the user says \"check my kitchen\", \"daily kitchen check\", \"anything I should know\", or \"what needs attention\". Not for full weekly planning or logging a receipt.\n---\n\n# Kitchen check\n\nBuilt to run unattended. The first pass only looks; nothing is written until the user explicitly approves a specific proposal.\n\n## 1. Look around (reading tools only)\n\n- `get_user_context`: household rules, expiring items (next 3 days), Household notes.\n- `get_pantry` with `expiringSoon: true`: expiring items with dates.\n- `show_meal_plan`: which of the next 3 days have no dinner.\n- `show_shopping`: staples missing from the list.\n\nDo not call any `manage_*`, `shop_for_meal_plan`, `post_cook`, or `process_receipt` during this step.\n\n## 2. Proposals\n\nReturn at most 5 proposals, most urgent first, one line each with the fix it would make:\n\n- Expiring: \"Spinach expires Thursday. Plan it into Wednesday dinner?\" (use `find_recipes` with `ingredients` and `forAllProfiles: true` to name a real recipe). Prefer a recipe with no household conflict noted in the results; if the only fit has a conflict, name the person and the conflict in the proposal line. Do not propose changing a dinner on a day with a `schedulingRules` theme (for example pizza night), and name the meal a proposal would replace.\n- Unplanned dinner: \"Nothing planned Friday. Want 2-3 ideas?\"\n- Missing staples: \"Eggs and milk are staples not on your list. Add them?\"\n\nIf nothing needs attention, say \"All clear\" in one line and stop.\n\nSkip any proposal the user already declined in this conversation. Never repeat it.\n\n## 3. Act only on approval\n\nFor each proposal the user approves, and only that one:\n\n- Plan a meal: `manage_meal_plan` action `set` (`date`, `dinner` or `dinnerRecipeId`). It returns a preview; once the user agrees, call again with `confirm: true`. Then `show_meal_plan`.\n- Add staples or items: `manage_shopping` action `add` with `items` and `storeName` if known. Then `show_shopping`.\n- Remove expired food: `manage_pantry` action `clear_expired` or `remove`, only after the user names what to remove.\n\nConfirm each write from the tool result. If it fails, say so and leave the proposal open.\n\n## Boundaries\n\n- \"No\", \"skip\", or silence means do nothing.\n- Never delete or clear anything without explicit approval of that exact change.\n- If a tool reports a limit, state it plainly and continue.\n- Keep the whole response short: proposals list, one question.\n"
}