← ChefSenseCONTENT HISTORY

Update to ChefSense

Snapshot Oct 27, 2026 · 06:07 UTC · version 1.2.0

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for get-started

Full description — Now says: Get started with ChefSense. Use the first time the user uses ChefSense, or when they ask what ChefSense can do.

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save ChefSense and check future changes in Following.

Up to 10 plugins free · no card required.

All fields and original values.

Full description

Before

Oct 24, 2026 · 13:41 UTC

Get started with ChefSense. Use when the user has just connected ChefSense or asks what it can do with their pantry, recipes, household or shopping list.

After

Oct 27, 2026 · 06:07 UTC

Get started with ChefSense. Use the first time the user uses ChefSense, or when they ask what ChefSense can do.

Skill instructions

Before

Oct 24, 2026 · 13:41 UTC

when the user has just connected ChefSense or asks what it can do with their pantry, recipes, household or shopping list. ChefSense keeps track of the user's kitchen: pantry items, saved recipes, a shopping list, and the diets, allergies...

After

Oct 27, 2026 · 06:07 UTC

the first time the user uses ChefSense, or when they ask what ChefSense can do. The user found ChefSense moments ago and knows nothing about it yet. Their pantry and recipe book are empty. Show them what ChefSense does in one exchange: t...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,24 +1,18 @@
 ---
 name: get-started
-description: Get started with ChefSense. Use when the user has just connected ChefSense or asks what it can do with their pantry, recipes, household or shopping list.
+description: Get started with ChefSense. Use the first time the user uses ChefSense, or when they ask what ChefSense can do.
 ---
 
-ChefSense keeps track of the user's kitchen: pantry items, saved recipes, a shopping list, and the diets, allergies and dislikes of everyone in their household.
+The user found ChefSense moments ago and knows nothing about it yet. Their pantry and recipe book are empty. Show them what ChefSense does in one exchange: they name three things from their kitchen, and ChefSense turns them into three recipes saved to their recipe book.
 
-When the user is getting started:
+1. If their first message is already a specific task, such as saving a recipe from a link, do that and skip this.
+2. Make the offer in a sentence or two, for example: "ChefSense keeps track of what's in your kitchen and turns it into recipes. Tell me three things in your fridge or pantry and I'll make you three recipes with them." If they opened with a question like what to make tonight, answer it with this offer.
+3. When they reply, add what they named with `add_pantry_items_bulk`. Two or five items are fine too. If they send a photo, read the items from it yourself instead of starting a scan. If they mention a diet or allergy, save it with `update_diet_profile` first so the recipes respect it.
+4. Call `generate_recipe` once, with a prompt built around their items, such as "three dinners using chicken thighs, spinach and rice". That one call makes three recipes, with pictures, and saves all three to their recipe book. It uses one of their monthly ChefSense recipe generations. Tell them the recipes are on their way; it can take a minute or two.
+5. Poll `list_recipes` until the three new recipes appear. For each, give the title, how long it takes and which of their items it uses. Offer to show one in full with `get_recipe`.
+6. Say in a sentence what ChefSense did: their items and three recipes are saved in their ChefSense account, so they can come back to them in any chat.
+7. Offer one more thing to try now: share a recipe link they love and get its shopping list, send a photo of a receipt or their fridge to see what to use first, or say what they eat or avoid so every recipe fits.
 
-1. Call `list_pantry` and `get_household` so you know what they have and who they cook for.
-2. Tell them briefly what you found (for example what's expiring soon and whose diets you'll respect).
-3. Offer two or three things to try next, such as:
-   - "What can I make tonight with what's expiring?"
-   - "Add what I just bought to my pantry."
-   - "Show my shopping list."
+If `generate_recipe` says they've reached their limit, write three recipes yourself from the same items and offer to save the one they like with `save_recipe`.
 
-Ground rules:
-
-- Before suggesting or generating recipes, check the pantry and household so suggestions use real ingredients and respect everyone's diets, allergies and dislikes.
-- Confirm with the user before any tool that changes their data. After a change, remind them they can say "undo that" (`undo_last_change`). Shopping list changes can't be undone.
-- `generate_recipe`, `iterate_recipe_start` and the scan tools run ChefSense's own recipe engine and scanner, which the user has a limited number of each month. If you already wrote the recipe or read the photo yourself, use `save_recipe` or `add_pantry_items_bulk` instead.
-- Recipe generation, refinement and scans run in the background. The tool returns an id; poll for the result rather than assuming it failed.
-- ChefSense can't guarantee a recipe is safe for an allergy. Remind users to check labels.
-- ChefSense doesn't place orders. The shopping list is a list only.
+ChefSense can't guarantee a recipe is safe for an allergy. If they mention one, remind them to check labels.
Full technical diff · 2 changed fields

changed /description

BEFORE
"Get started with ChefSense. Use when the user has just connected ChefSense or asks what it can do with their pantry, recipes, household or shopping list."
AFTER
"Get started with ChefSense. Use the first time the user uses ChefSense, or when they ask what ChefSense can do."

changed /skill_md_contents

BEFORE
"---\nname: get-started\ndescription: Get started with ChefSense. Use when the user has just connected ChefSense or asks what it can do with their pantry, recipes, household or shopping list.\n---\n\nChefSense keeps track of the user's kitchen: pantry items, saved recipes, a shopping list, and the diets, allergies and dislikes of everyone in their household.\n\nWhen the user is getting started:\n\n1. Call `list_pantry` and `get_household` so you know what they have and who they cook for.\n2. Tell them briefly what you found (for example what's expiring soon and whose diets you'll respect).\n3. Offer two or three things to try next, such as:\n   - \"What can I make tonight with what's expiring?\"\n   - \"Add what I just bought to my pantry.\"\n   - \"Show my shopping list.\"\n\nGround rules:\n\n- Before suggesting or generating recipes, check the pantry and household so suggestions use real ingredients and respect everyone's diets, allergies and dislikes.\n- Confirm with the user before any tool that changes their data. After a change, remind them they can say \"undo that\" (`undo_last_change`). Shopping list changes can't be undone.\n- `generate_recipe`, `iterate_recipe_start` and the scan tools run ChefSense's own recipe engine and scanner, which the user has a limited number of each month. If you already wrote the recipe or read the photo yourself, use `save_recipe` or `add_pantry_items_bulk` instead.\n- Recipe generation, refinement and scans run in the background. The tool returns an id; poll for the result rather than assuming it failed.\n- ChefSense can't guarantee a recipe is safe for an allergy. Remind users to check labels.\n- ChefSense doesn't place orders. The shopping list is a list only.\n"
AFTER
"---\nname: get-started\ndescription: Get started with ChefSense. Use the first time the user uses ChefSense, or when they ask what ChefSense can do.\n---\n\nThe user found ChefSense moments ago and knows nothing about it yet. Their pantry and recipe book are empty. Show them what ChefSense does in one exchange: they name three things from their kitchen, and ChefSense turns them into three recipes saved to their recipe book.\n\n1. If their first message is already a specific task, such as saving a recipe from a link, do that and skip this.\n2. Make the offer in a sentence or two, for example: \"ChefSense keeps track of what's in your kitchen and turns it into recipes. Tell me three things in your fridge or pantry and I'll make you three recipes with them.\" If they opened with a question like what to make tonight, answer it with this offer.\n3. When they reply, add what they named with `add_pantry_items_bulk`. Two or five items are fine too. If they send a photo, read the items from it yourself instead of starting a scan. If they mention a diet or allergy, save it with `update_diet_profile` first so the recipes respect it.\n4. Call `generate_recipe` once, with a prompt built around their items, such as \"three dinners using chicken thighs, spinach and rice\". That one call makes three recipes, with pictures, and saves all three to their recipe book. It uses one of their monthly ChefSense recipe generations. Tell them the recipes are on their way; it can take a minute or two.\n5. Poll `list_recipes` until the three new recipes appear. For each, give the title, how long it takes and which of their items it uses. Offer to show one in full with `get_recipe`.\n6. Say in a sentence what ChefSense did: their items and three recipes are saved in their ChefSense account, so they can come back to them in any chat.\n7. Offer one more thing to try now: share a recipe link they love and get its shopping list, send a photo of a receipt or their fridge to see what to use first, or say what they eat or avoid so every recipe fits.\n\nIf `generate_recipe` says they've reached their limit, write three recipes yourself from the same items and offer to save the one they like with `save_recipe`.\n\nChefSense can't guarantee a recipe is safe for an allergy. If they mention one, remind them to check labels.\n"
Full snapshot data
{
  "description": "Get started with ChefSense. Use the first time the user uses ChefSense, or when they ask what ChefSense can do.",
  "included_files": [],
  "name": "get-started",
  "skill_md_contents": "---\nname: get-started\ndescription: Get started with ChefSense. Use the first time the user uses ChefSense, or when they ask what ChefSense can do.\n---\n\nThe user found ChefSense moments ago and knows nothing about it yet. Their pantry and recipe book are empty. Show them what ChefSense does in one exchange: they name three things from their kitchen, and ChefSense turns them into three recipes saved to their recipe book.\n\n1. If their first message is already a specific task, such as saving a recipe from a link, do that and skip this.\n2. Make the offer in a sentence or two, for example: \"ChefSense keeps track of what's in your kitchen and turns it into recipes. Tell me three things in your fridge or pantry and I'll make you three recipes with them.\" If they opened with a question like what to make tonight, answer it with this offer.\n3. When they reply, add what they named with `add_pantry_items_bulk`. Two or five items are fine too. If they send a photo, read the items from it yourself instead of starting a scan. If they mention a diet or allergy, save it with `update_diet_profile` first so the recipes respect it.\n4. Call `generate_recipe` once, with a prompt built around their items, such as \"three dinners using chicken thighs, spinach and rice\". That one call makes three recipes, with pictures, and saves all three to their recipe book. It uses one of their monthly ChefSense recipe generations. Tell them the recipes are on their way; it can take a minute or two.\n5. Poll `list_recipes` until the three new recipes appear. For each, give the title, how long it takes and which of their items it uses. Offer to show one in full with `get_recipe`.\n6. Say in a sentence what ChefSense did: their items and three recipes are saved in their ChefSense account, so they can come back to them in any chat.\n7. Offer one more thing to try now: share a recipe link they love and get its shopping list, send a photo of a receipt or their fridge to see what to use first, or say what they eat or avoid so every recipe fits.\n\nIf `generate_recipe` says they've reached their limit, write three recipes yourself from the same items and offer to save the one they like with `save_recipe`.\n\nChefSense can't guarantee a recipe is safe for an allergy. If they mention one, remind them to check labels.\n"
}

SHA-256 of public snapshot: 43483056be4e0c650b9adb447e36df1a4c0fab592a47b4423e9a9054f1a840fc