← CalcIng EngineeringCONTENT HISTORY
WHAT CHANGED
Update to CalcIng Engineering
Snapshot Nov 11, 2026 · 00:09 UTC · version 0.1.9
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save CalcIng Engineering 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": "Pass the result of one calcing calculation on as the input of another calcing app (saas.calcing.de tools of this plugin). Use when the user wants a follow-up calculation from a result they just got, for example \"now check the key on this shaft\" or \"use this bearing result in the next step\".",
"included_files": [],
"name": "result-handoff",
"skill_md_contents": "---\nname: result-handoff\ndescription: Pass the result of one calcing calculation on as the input of another calcing app (saas.calcing.de tools of this plugin). Use when the user wants a follow-up calculation from a result they just got, for example \"now check the key on this shaft\" or \"use this bearing result in the next step\".\n---\n\n# Hand a calcing result on to the next app\n\nThe calcing tools include a result hand-off service. Find it in the `services` of the list tool\n`calcing_list_apps`: it names its actions (`dry-run`, `execute`), their tools and their\n`required_fields` (`from_app`, `to_app`). Its `body_shape` is `flach`: the fields go at the top\nlevel of the tool's `input` object. Use only the tools the list names.\n\n1. **Source.** The source is a complete calculation result envelope returned by a calcing `solve`\n (or hand-off `execute`) call in this conversation. Pass it as `from_result`, with `from_app` set to\n that app's `registry_key` and `to_app` to the target app's `registry_key`. Do not edit or shorten\n the envelope, and do not build one by hand.\n2. **Dry run first.** Call the `dry-run` tool. It prepares the transfer without calculating and\n reports the target's missing required fields. Show the user which values were transferred and which\n are missing.\n3. **Missing values.** Ask the user for each missing value with its unit. Do not fill them yourself.\n4. **Execute.** Only when nothing required is missing and the user agrees, call the `execute` tool.\n It transfers and calculates, and returns the target's full envelope, which can be the next step's\n `from_result`.\n If the user's missing values cannot be passed in the hand-off call, run the target app through the\n `engineering-calculation` skill instead (schema, validate, solve), starting from the inputs the\n dry run prepared.\n5. **Report** the target's result as the `engineering-calculation` skill describes: values with units,\n every warning and note, provenance, no conformity claims beyond what the result says.\n\nIf a hand-off call fails, report the `error` code and message and stop. Never substitute an estimated\nvalue for a failed transfer or calculation. `execute` calculates and is not read-only, so the host may\nask the user to confirm it; `dry-run` is read-only.\n"
}SHA-256 of public snapshot: b245b6d3a21e13c73a4f88020f9a293a0de121fa1f289bb782a04b1ac2e27b1b