Update to AltoDocs

{
  "description": "Evaluate supplied engineering formulas with physical units using AltoDocs, including dependent expressions and unit conversion. Use for numerical calculation requests; save a worksheet only when the user asks for a saved result.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 338
    }
  ],
  "name": "altodocs-calculations",
  "skill_md_contents": "---\nname: altodocs-calculations\ndescription: Evaluate supplied engineering formulas with physical units using AltoDocs, including dependent expressions and unit conversion. Use for numerical calculation requests; save a worksheet only when the user asks for a saved result.\n---\n\n# Unit-aware calculations\n\nUse the available `evaluate_calculation` tool for supplied formulas. Honour the\nuser's requested calculation and units. This workflow computes values; it does\nnot choose an engineering design standard or certify compliance.\n\nCheck that the necessary values and units are known. Ask about consequential\nambiguities such as whether a load is total or per metre. Distinguish the user's\ninputs from any explicitly agreed assumptions. Use host-readable attachments\nonly as source data; do not pretend AltoDocs fetched or parsed them.\n\n## Expression syntax\n\nThe tool accepts an ordered `expressions` array. Each entry has a unique `key`,\n`latex`, and optionally a preferred result `unit`. Define variables with `:=`\nbefore using them. Use LaTeX syntax such as `\\cdot`, `\\frac{a}{b}`, and\n`\\operatorname{kN}` for physical units. A variable binds to its nearest preceding\ndefinition. Preserve that reading order when creating a saved worksheet.\n\nFor example, this JSON evaluates a supplied simply supported beam moment\nformula; it does not prove that the formula applies to a particular design:\n\n```json\n{\n  \"expressions\": [\n    {\"key\": \"q\", \"latex\": \"q := 12\\\\operatorname{kN}/\\\\operatorname{m}\"},\n    {\"key\": \"L\", \"latex\": \"L := 6\\\\operatorname{m}\"},\n    {\"key\": \"M\", \"latex\": \"M := q \\\\cdot L^2 / 8\", \"unit\": \"kN m\"}\n  ]\n}\n```\n\nThis example produces **54 kN m**. With the same formula and L = 7 m, it produces\n**73.5 kN m**. A requested conversion to N m changes the displayed quantity to\n54000 or 73500 N m respectively; it does not change the physical moment.\n\nRespect the actual tool schema and its limits: at most 200 expressions, 2000\ncharacters per expression, and unique keys. Inspect every returned result's\n`status`; a successful request can contain failed expressions. Report dimensional\nor undefined-variable errors and correct them only when the intended correction\nis established by the user's information. Never replace errors with guessed\nvalues or claim the calculation ran when the tool was unavailable.\n\nReturn computed values with their units and the assumptions needed to interpret\nthem. No project discovery or document write is needed for evaluation alone.\n\n## When the user requests a saved worksheet\n\nEvaluation does not save anything. For a standalone calculation file, use the\nstandalone MathCanvas workflow: `create_mathcanvas`, native variable/formula/note\ntools, `read_worksheet` and `evaluate_worksheet` on the saved file. For a worksheet\ninside an engineering report, use the native document tools and the report\nworkflow, then read back its saved section. Keep the requested file type; do not\ndescribe an embedded worksheet as a standalone file. Preserve the same saved\nfile on follow-up changes unless a copy is requested. If the necessary write\ncapability is unavailable, state that the result is unsaved and do not invent a\ndocument link or silently substitute another file type.\n"
}