← BiosimulantCONTENT HISTORY
WHAT CHANGED
Update to Biosimulant
Snapshot Nov 6, 2026 · 12:12 UTC · version 1.1.1
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Biosimulant 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": "Find a published model to reuse, adapt a model in a private lab, or design a model from evidence. Use when the user wants to choose, build, or revise an executable model or plan its tests.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 264
},
{
"relative_path": "references/requirements/assets/master-template.md",
"size_in_bytes": 22339
},
{
"relative_path": "references/requirements/references/biosimulant-runtime.md",
"size_in_bytes": 8494
},
{
"relative_path": "references/requirements/references/examples/digital-twin.md",
"size_in_bytes": 12903
},
{
"relative_path": "references/requirements/references/examples/generative.md",
"size_in_bytes": 12831
},
{
"relative_path": "references/requirements/references/examples/mechanistic.md",
"size_in_bytes": 12759
},
{
"relative_path": "references/requirements/references/examples/optimization.md",
"size_in_bytes": 12492
},
{
"relative_path": "references/requirements/references/examples/predictive-ml.md",
"size_in_bytes": 12593
},
{
"relative_path": "references/requirements/references/examples/statistical-estimation.md",
"size_in_bytes": 11989
},
{
"relative_path": "references/requirements/references/suite-lifecycle.md",
"size_in_bytes": 11733
},
{
"relative_path": "references/requirements/scripts/spec_utils.py",
"size_in_bytes": 4605
},
{
"relative_path": "references/requirements/scripts/start_mrs.py",
"size_in_bytes": 1783
},
{
"relative_path": "references/requirements/scripts/validate_mrs.py",
"size_in_bytes": 4978
},
{
"relative_path": "references/requirements/workflow.md",
"size_in_bytes": 7188
},
{
"relative_path": "references/technical-plan/assets/master-template.md",
"size_in_bytes": 26470
},
{
"relative_path": "references/technical-plan/references/biosimulant-runtime.md",
"size_in_bytes": 9348
},
{
"relative_path": "references/technical-plan/references/examples/digital-twin.md",
"size_in_bytes": 12896
},
{
"relative_path": "references/technical-plan/references/examples/generative.md",
"size_in_bytes": 11000
},
{
"relative_path": "references/technical-plan/references/examples/mechanistic.md",
"size_in_bytes": 10191
},
{
"relative_path": "references/technical-plan/references/examples/optimization.md",
"size_in_bytes": 10285
},
{
"relative_path": "references/technical-plan/references/examples/predictive-ml.md",
"size_in_bytes": 10712
},
{
"relative_path": "references/technical-plan/references/examples/statistical-estimation.md",
"size_in_bytes": 8995
},
{
"relative_path": "references/technical-plan/references/mts-suite-guidance.md",
"size_in_bytes": 13394
},
{
"relative_path": "references/technical-plan/references/suite-lifecycle.md",
"size_in_bytes": 11733
},
{
"relative_path": "references/technical-plan/scripts/spec_utils.py",
"size_in_bytes": 4335
},
{
"relative_path": "references/technical-plan/scripts/start_mts.py",
"size_in_bytes": 1749
},
{
"relative_path": "references/technical-plan/scripts/validate_mts.py",
"size_in_bytes": 7801
},
{
"relative_path": "references/technical-plan/workflow.md",
"size_in_bytes": 9507
}
],
"name": "build-or-adapt-a-model",
"skill_md_contents": "---\nname: build-or-adapt-a-model\ndescription: Find a published model to reuse, adapt a model in a private lab, or design a model from evidence. Use when the user wants to choose, build, or revise an executable model or plan its tests.\n---\n\n# Build or adapt a model\n\nInspect the connected server's available tools and schemas. Explain model choices and approval requests in plain English, with the relevant scientific detail.\n\n1. Clarify the scientific question, available data, and what the model needs to predict or explain. Check the user's existing lab before making a new one. When reusing a published model, inspect the exact release, inputs, outputs, units, assumptions, runtime, license, and attribution. Explain what can be reused and what needs to change.\n2. For implementation, preserve source references and executable interfaces. Work in the correct private lab or copy, and preview the exact edits through the connected server. Apply them only under the current permission and approval rules. Test the behavior the user needs with real or clearly labeled example inputs. Report what was saved and which tests actually ran.\n3. For a formal design request, use [Define what the model must do](references/requirements/workflow.md) to capture requirements and tests that could demonstrate them. Use [Plan how to build and test the model](references/technical-plan/workflow.md) when the requirements are approved. Keep templates and validation guidance with these steps. They are optional for ordinary modeling work.\n\nExample: “Find a published model I can adapt for my question. Explain what it assumes and what I'd need to change.”\n"
}SHA-256 of public snapshot: 95adf13d14cc5bda5d50a0f9578a7afc0b3789fd45dc216135e35fac28fd36ee