{"id":98845,"plugin_id":"plugin_asdk_app_6ad7d385b7f481919b104e27f55a36ca","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-16T18:15:49.548Z","digest":"81def4079566a1ffdf0f2edc1c8ac147668ea5307865a65960cd9b3d84ebcf39","against":null,"payload":{"description":"Import confectionery recipes from an external source into Formul.io through its MCP server, keeping source quantities, phases and method intact. Use when the user wants to import, digitize, transcribe, save or move in a recipe that already exists somewhere else, such as pasted text, a cookbook page, a web page, a photo you can read, or a file you can read, one recipe at a time. Triggers include \"import this recipe\", \"add this recipe to Formul.io\", \"digitize my recipe book\", \"импортируй рецепт\", \"перенеси рецепт в Formul.io\", \"оцифруй рецепты из файла\". Do not use it for a formula invented in the conversation; that belongs to develop-recipe.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":419}],"name":"import-recipe","skill_md_contents":"---\nname: import-recipe\ndescription: Import confectionery recipes from an external source into Formul.io through its MCP server, keeping source quantities, phases and method intact. Use when the user wants to import, digitize, transcribe, save or move in a recipe that already exists somewhere else, such as pasted text, a cookbook page, a web page, a photo you can read, or a file you can read, one recipe at a time. Triggers include \"import this recipe\", \"add this recipe to Formul.io\", \"digitize my recipe book\", \"импортируй рецепт\", \"перенеси рецепт в Formul.io\", \"оцифруй рецепты из файла\". Do not use it for a formula invented in the conversation; that belongs to develop-recipe.\nlicense: MIT\ncompatibility: Requires the Formul.io MCP server (https://api.formul.io/mcp) with the recipes:read, recipes:write, ingredients:read and calculate scopes; diagnose is optional. Write scopes are granted only when requested at connection.\nmetadata:\n  author: Formul.io\n  version: \"1.0\"\n---\n\n# Import a recipe into Formul.io\n\nThe goal is a faithful copy of someone else's recipe. Transcribe the source as\nit is written and do not improve it. Optimizing is a separate step that the\nuser asks for after the import.\n\n## Pick the path\n\n| Source | Path |\n|---|---|\n| One recipe you can read: pasted text, a web page, a photo you can see, a book page | **Structured import**: `import_recipe` |\n| A file you can read that holds a few recipes | Read it and import each recipe separately, one `import_recipe` call per recipe, each previewed with the user |\n| A long file, a whole recipe book, or a file you cannot read | Point the user to the file import in the Formul.io app, which reviews the whole file and asks about doubtful lines there |\n| A scanned PDF without a text layer, or a photo you cannot read | Point the user to the photo import in the Formul.io app |\n| A Formul.io export file | Tell the user to restore it in the app, which reads it back exactly |\n| A formula the user and you are composing now | Not an import. Use `develop-recipe` |\n\n## Import one recipe\n\n### 1. Transcribe\n\nRecord these fields from the source:\n\n- `name`, `description`, and `source_url` for attribution. The server does not\n  fetch the URL.\n- Every ingredient line **in source order**. Keep a repeated ingredient as\n  separate lines when it enters at different points, for example water in the\n  syrup and water that dissolves the acid.\n- The full method as a `general` note in Markdown, step by step, in the source\n  language. Put source tips in `tip` notes and warnings in `warning` notes. The\n  tool expects the method to be kept, so never drop it.\n\n### 2. Convert every quantity to grams\n\n`quantity_g` must be greater than 0. Weights convert directly. For everything\nelse, convert the amount and keep the original in the line `note`, for example\n`source: 2 sheets`:\n\n- Volumes: multiply by the ingredient's density (cream ≈ 1.0 g/mL, glucose\n  syrup ≈ 1.4 g/mL, honey ≈ 1.4 g/mL).\n- Counts: an egg without its shell ≈ 50 g, a yolk ≈ 18 g, a white ≈ 32 g.\n  Gelatin sheets vary by grade (gold ≈ 2 g, silver ≈ 2.5 g, bronze ≈ 3.3 g).\n- Baker's percentages: ask for the total batch weight first.\n\nEvery conversion is an assumption. List the conversions in the review in step 5.\nWhen no reasonable conversion exists, ask the user.\n\n### 3. Choose the calculator, style and phases\n\n- `calculator_type` is one of `ganache`, `caramel`, `dragee`, `patedefruit`,\n  `icecream`, `nougat`, `mousse`, or `recipe` (Custom Recipe, freeform) when\n  the product fits none of them.\n- Call `get_calculator_guide(calculator_type, section=\"overview\")`. Pick the\n  `available_styles` entry that matches the source and write it to\n  `settings[<style_setting>]`, using the key the guide names, such as\n  `ganache_type`. When the style is unclear, leave the default.\n- Set `phase` on each line when 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 `acid_solution`,\n  used for both the acid and its dilution water. Use `main` for everything else.\n- Leave out `stages`. The calculator generates its process graph from the\n  settings and phases.\n\n### 4. Preview (writes nothing)\n\nCall `import_recipe(mode=\"preview\")` with every field from steps 1–3. Each line\ncomes back with a `resolution.status`:\n\n| Status | Action |\n|---|---|\n| `matched` / `recommended` | Use its `ingredient_id` |\n| `alternative` | Pick a candidate by **actual composition**: cream 35 % and 30 % change the result, and so do dark chocolate 64 % and 70 %. When the choice moves the numbers and the source does not settle it, ask the user. A generic name such as \"sugar\" never binds a specific product. |\n| `needs_create` | You need a composition. Rows under `nearest` are marked `match.weak`: they only resemble the name (another percentage, a shared word), so never use one without asking the user. Try `search_ingredients` first; its `reference_candidates` carry USDA/CIQUAL data. Otherwise use the manufacturer's data sheet or ask the user. **Never invent a composition.** |\n| `incomplete` | The search failed. Retry later and do not create a duplicate. |\n\nFor a branded product, prefer the exact product over a generic one. Keep any\nbrand the source names.\n\n### 5. Review with the user\n\nShow a table with the source line, the library ingredient or the new custom\ningredient with its data source, the grams, and the phase. Below it, list the\nunit conversions and any assumptions. Wait for explicit approval before\nwriting.\n\n### 6. Confirm (this writes)\n\nCall `import_recipe(mode=\"confirm\")` with the same `name`, `calculator_type`,\n`description`, `settings`, `tags`, `notes` and `source_url`. Add `resolved[]`\nwith **one entry per ordered line**, carrying the same name, quantity, phase\nand note as in the preview, plus **exactly one** of:\n\n- `ingredient_id`, or\n- `create{...}` with percentages by mass. `water_pct`, `carbohydrate_pct`,\n  `fat_pct` and `protein_pct` are required. `carbohydrate_pct` excludes fibre,\n  and `alcohol_pct` is the ethanol mass fraction, not ABV. When the same new\n  ingredient appears on several lines, repeat the identical `create{}` payload\n  on each line.\n\n### 7. Report\n\nGive the recipe's name and `url` from the result, never a bare id. Mention any\n`created_ingredients`, `post_commit_warning` or `detail_error`. You can offer\n`analyze_recipe` as a next step, but do not change the imported recipe unless\nthe user asks.\n\n## Rules\n\n- Do not change the source's proportions, substitute ingredients, or \"fix\"\n  quantities during an import.\n- Persist only after the user has approved the preview.\n- Resolve ingredients in batches and do not search for one name at a time.\n- Use grams and °C throughout.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}