← Formul.ioCONTENT HISTORY
WHAT CHANGED
Update to Formul.io
Snapshot Nov 16, 2026 · 18:15 UTC · version 0.3.4
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Formul.io and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Develop a new professional confectionery recipe from a brief with the Formul.io MCP server. The brief is turned into a formula, checked against the calculator's target bands without saving, iterated, and saved only after the user approves. Use when the user asks you to create, develop, formulate or design a new ganache, caramel, pâte de fruit, ice cream or sorbet, nougat, mousse, dragée or custom recipe, especially with targets such as shelf life, water activity, texture, sugar level, or vegan and allergen constraints. Triggers include \"create a ganache for bonbons with 3 weeks shelf life\", \"develop a vegan caramel\", \"придумай рецепт\", \"разработай ганаш\", \"сделай рецептуру под ТЗ\". Do not use it to transcribe an existing recipe (import-recipe), to diagnose a saved recipe (improve-recipe), or to design several recipes as a line (prototype-collection).",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 448
}
],
"name": "develop-recipe",
"skill_md_contents": "---\nname: develop-recipe\ndescription: Develop a new professional confectionery recipe from a brief with the Formul.io MCP server. The brief is turned into a formula, checked against the calculator's target bands without saving, iterated, and saved only after the user approves. Use when the user asks you to create, develop, formulate or design a new ganache, caramel, pâte de fruit, ice cream or sorbet, nougat, mousse, dragée or custom recipe, especially with targets such as shelf life, water activity, texture, sugar level, or vegan and allergen constraints. Triggers include \"create a ganache for bonbons with 3 weeks shelf life\", \"develop a vegan caramel\", \"придумай рецепт\", \"разработай ганаш\", \"сделай рецептуру под ТЗ\". Do not use it to transcribe an existing recipe (import-recipe), to diagnose a saved recipe (improve-recipe), or to design several recipes as a line (prototype-collection).\nlicense: MIT\ncompatibility: Requires the Formul.io MCP server (https://api.formul.io/mcp) with the calculate, diagnose, ingredients:read, recipes:read and recipes:write scopes; ingredients:write only to add a custom ingredient. Write scopes are granted only when requested at connection.\nmetadata:\n author: Formul.io\n version: \"1.1\"\n---\n\n# New recipe from a brief\n\nWork through every candidate formula in memory and save once. Every metric\ncomes from the Formul.io engine; never estimate a number yourself when a tool\ncan compute it. Ask questions and explain results in the user's language.\n\nUse the connected Formul.io MCP tools and their current input schemas; the host\nmay prefix tool names. If a required tool or scope is unavailable, say what\ncannot be calculated or saved and stop that operation. Never invent tool\nresults, ingredient ids or a successful save.\n\n## 1. Pin down the brief\n\nEstablish these points. Ask only about the ones that are missing **and** would\nchange the formula; take a stated default for the rest, and do not ask the user\nto repeat what the conversation already says.\n\n| Point | Maps to | Default if unstated |\n|---|---|---|\n| Product | `calculator_type` + style | Ask, since it decides everything else |\n| Batch size | total grams | 1000 g, stated |\n| Storage and target life | style + `aw` band; `microbial_growth` and `storage_requirement` in the metrics; `shelf_life_room_temp_days` as a reference | the style's Aw band |\n| Constraints | vegan, allergen-free, sugar ceiling, no polyols | none |\n| Named products | exact brands the user owns | favourites (see step 3) |\n| Texture and use | style: bonbon frame, enrobed, piping, spread… | the calculator's default style |\n\nIf the user works inside a collection, call `get_collection(collection_id)`.\nIts `instructions` and `requirements` are project preferences to honour within\nthe user's request.\n\n## 2. Read the target\n\nCall `get_calculator_guide(calculator_type, style=...)`. The default section\nreturns:\n\n- `optimal_ranges` for **this style**. Bands differ sharply between styles; a\n sorbet's fat band is not an ice cream's.\n- `formulation_rules`: the stabilizers, emulsifiers and anti-crystallization\n agents a professional formula needs. Follow them.\n- `settings_schema` and `style_setting`, the settings key that stores the style\n (for example `ganache_type`).\n\nFetch the guide once per calculator and style and reuse it. Do not invent\nprocess temperatures, times or yield the guide and the user did not give; label\na process choice of your own as a proposal.\n\n## 3. Draft and resolve\n\n1. Write a first formula from professional practice so that the ingredients add\n up to the batch weight. It is a new formulation, distinct from any source\n recipe's quantities.\n2. Resolve **all** the names in one `resolve_ingredients` call (at most 25\n names):\n - `matched` / `recommended`: use the id.\n - `alternative`: pick by actual composition (fat %, cocoa %, water %). An\n alternative or a generic category name is not an exact match for a named\n product.\n - `nearest` rows (`match.weak`) only resemble the name, such as another\n percentage of the same line. Never use one without the user's consent.\n - `needs_create`: call `search_ingredients` with `mode=\"selection\"` and\n characteristics, for example\n `{\"field\": \"fat\", \"operator\": \"near\", \"value\": 35}` for 35 % fat\n cream. If nothing fits, propose\n `create_ingredient` with sourced composition and **ask first**, because it\n writes to the user's library. Never invent a composition.\n3. When the user named nothing, prefer rows flagged `is_favorite` and then\n `is_favorite_brand`. Never swap a product the user named.\n4. Give each line a phase where the calculator routes by phase: ganache\n `chocolate`/`cream`; mousse `base`/`cream`/`gelatin_bloom`; nougat\n `meringue`/`syrup`/`honey`; caramel `finish`; pâte de fruit\n `acid_solution`. Use `main` for everything else. Send the same phases in\n every ad-hoc call and in `create_recipe`, so the prototype computes exactly\n the process the saved recipe will run.\n\n## 4. Iterate without saving\n\n- Call `simulate_changes` with an **ad-hoc baseline**: `calculator_type`,\n `ingredients` (`ingredient_id` + `quantity_g` + `phase`), and `settings`\n including the style key. Put every candidate adjustment into **one call**,\n with up to 20 named `scenarios` of `add`/`remove`/`update`/`substitute`\n changes. A change's amount is `quantity` in grams, not `quantity_g`. Each\n scenario returns its deltas against the bands.\n- A row that a scenario `add` change introduces enters as `main`. To try an\n addition in another phase, put it in the baseline `ingredients` with its phase\n instead.\n- When you need a single formula's full metrics, use `get_recipe_metrics` with\n the same ad-hoc shape.\n- Read the bands carefully. A missing metric is not a passing result. For `aw`\n and free water, being below the band is a texture or yield miss, not a safety\n risk. Adding water to close that gap makes the product **less** stable.\n- If proportions stop moving a metric toward its band, call\n `advise_formulation` with the ad-hoc formula. It reports which metrics the\n current ingredients cannot reach and which class of ingredient would unlock\n them, such as a humectant or invert sugar. Add that component and do not keep\n re-weighing.\n- Stop after about three rounds and show the user where things stand. Do not\n loop silently.\n\n## 5. Present for approval\n\nShow:\n\n- A formula table with ingredient, grams, % of the batch, and phase.\n- Key metrics against their bands, marking each in band or out of band with the\n direction.\n- The trade-offs you chose and anything still out of band, with the reason.\n- One `show_card` call for the final formula (`kind:\"metrics\"`, or\n `kind:\"comparison\"` with the final `simulate_changes` arguments), so the user\n sees the card. The calculation tools show no card, so call it only once.\n\nShelf life and water activity are model predictions. For a product that will be\nsold, recommend confirming them with a measurement, such as a water activity\nmeter or a challenge test.\n\n## 6. Save (after an explicit yes)\n\nAn instruction to save or create the recipe in Formul.io is that yes; do not ask\nfor it again. A request to explore or compare is not permission to write.\n\n1. Call `create_recipe` with `name`, `calculator_type`, `description` (the brief\n in one sentence), `tags`, `settings` (with the style key), and `ingredients`\n as `ingredient_id` + `quantity_g` + `phase`.\n2. If the result has `status: \"resolution_needed\"`, resolve the listed names and\n retry. Retrying is safe because nothing was saved. If the outcome of a write\n is ambiguous, check `list_recipes` for the recipe before creating it again.\n3. The receipt carries the new recipe in `entity` (`id`, `name`, `url`). Call\n `analyze_recipe` with `entity.id` and report the quality score and any\n flagged issues. Fix an issue only if the user asks, using `update_recipe`\n with `save_as_version: true` and the `revision` from `get_recipe` as\n `expected_revision`.\n4. Offer to record the design reasoning with\n `save_recipe_note(note_type=\"rationale\")`. For example: why 12 % invert sugar,\n or why this couverture.\n5. Give the recipe's name and `url`, never a bare id.\n\nEvery plan can create recipes and save notes. If a write returns\n`entitlement_required`, that tool is a Pro feature on this account. When it is\n`create_ingredient`, save the formula with `import_recipe` (`mode=\"confirm\"`),\nwhose `create{...}` lines add the custom ingredients. Otherwise say so with the\nplans link from the refusal, do not retry, and give the user the final formula\ntable so they can enter it in the app.\n\n## Rules\n\n- Never compromise food safety or declared allergens to hit a metric.\n- Use grams and °C, and professional formulations only.\n- Do not save intermediate drafts. Save only the formula the user approved.\n- To modify an existing recipe, use `update_recipe`. Use\n `create_recipe(from_recipe_id=...)` only when the user wants a separate copy.\n"
}SHA-256 of public snapshot: c107375504ec59a584d7a4571a35f1f7d066499ac787dc8a4253d276bd1e505c