← 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": "Prepare or repeat a Biosimulant computational experiment using a known lab, inputs, and settings. Use for new runs, reruns, or comparisons that require fresh compute and explicit approval.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 269
}
],
"name": "run-or-repeat-an-experiment",
"skill_md_contents": "---\nname: run-or-repeat-an-experiment\ndescription: Prepare or repeat a Biosimulant computational experiment using a known lab, inputs, and settings. Use for new runs, reruns, or comparisons that require fresh compute and explicit approval.\n---\n\n# Run or repeat an experiment\n\nCheck the connected server's tool schemas and current session policy. Explain the setup and approval in plain English, using exact quantities and units.\n\n1. Resolve the exact lab and revision. For a repeat, retrieve the original run and use its saved inputs, parameters, and bounds. Show any requested changes or missing files. If the same setup cannot be recreated, explain the difference before preparing a substitute.\n2. Prepare the plan through the connected service. Show the inputs, settings, compute limits, cost or pending estimate, expiry, and blockers. Follow the server's current approval rules and show its Studio review link when provided. If asked to prepare or wait for approval, stop at the plan. A chat response, plan ID, or hash by itself does not resolve a required Studio approval. A changed or expired plan needs a fresh review.\n3. When authorized to execute, use the exact approved plan and check the resulting run through its terminal outcome. Report the actual completion or failure and link to saved results and files when the server provides them. An inspection request never needs a fresh run.\n\nExample: “Prepare a rerun of my saved Boltz-2 experiment. Show me the inputs, settings, and estimated cost before I approve it.”\n"
}SHA-256 of public snapshot: 36fd5bdad7baf1efd850d71e55241c96705ba9cd1f654ca1c671126caa982cd4