← InductiveCONTENT HISTORY

Update to Inductive

Snapshot Sep 30, 2026 · 22:51 UTC · version 2.0.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "name": "compare-analogs",
  "description": "Compare molecular-property predictions across analogs with Inductive Bio using matched models, explicit deltas, and cautious interpretation. Use for analog ranking, property trends, or reference-relative comparisons.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 321
    }
  ],
  "skill_md_contents": "---\nname: compare-analogs\ndescription: Compare molecular-property predictions across analogs with Inductive Bio using matched models, explicit deltas, and cautious interpretation. Use for analog ranking, property trends, or reference-relative comparisons.\n---\n\n# Compare molecular analogs\n\nFollow the shared requirements in the `index` skill. Do not use this skill without applying those requirements.\n\n## Inputs\n\nCollect:\n\n- At least two compounds with distinct labels and exact SMILES.\n- Requested properties.\n- A reference compound when deltas are requested.\n- A direction or target range for each ranking criterion.\n- Any project pH, diversity constraint, or maximum shortlist size relevant to the decision.\n\nIf the user asks for the best compound without defining the desired direction or range, ask for the decision criterion. Do not assume that higher or lower is universally better.\n\nIf any structure is identified as confidential, obtain explicit confirmation before sending the structures to the connector.\n\n## Workflow\n\n1. Call `list_available_models` and resolve the requested properties to live model identifiers.\n2. Call `predict_properties` with the same selected model set for every analog, using the exact live MCP schema.\n3. Preserve the returned values and units. Do not compare values across different model identifiers or incompatible units as if they were directly equivalent.\n4. Build a comparison table containing label, exact SMILES, model identifier, property or assay, prediction, units, and status.\n5. When a reference is defined, compute signed deltas as `analog prediction - reference prediction` within each matched model and unit. State that convention.\n6. Rank only against criteria supplied by the user. Show ties and missing values explicitly, and do not rank failed or missing predictions as though they were numeric.\n7. Separate the result into returned predictions, derived deltas or rankings, and scientific interpretation.\n\n## Compound-series analysis\n\n- **Triage:** state the exact rules before applying them. If the user gives a qualitative rule such as \"moderate LogD,\" translate it into a clearly labeled provisional criterion or ask for a project-specific range when the distinction could change the decision. Keep every input compound and failed prediction visible.\n- **Shortlisting:** use only completed, comparable results; honor the requested maximum; preserve structural diversity when the structures support that assessment; and explain that the shortlist is assistant-side reasoning rather than an additional Inductive Bio prediction.\n- **Relationship and grouping analysis:** include only matched, nonmissing values in each comparison, report the number of compounds used, and identify apparent trends or clusters as descriptive. Do not claim mechanistic causality or statistical significance without an appropriate analysis.\n- **Results handoff:** organize completed results with compound ID, input SMILES, model name or property, model ID, predicted value, units, and status. Add assumptions, failures, and open questions separately. Do not claim a native export endpoint.\n\n## Interpretation boundary\n\nDescribe observed model trends without assigning causality to a structural change unless the comparison supports it and relevant confounders are acknowledged. Do not treat a favorable LogD, pKa, or other isolated prediction as proof of permeability, absorption, safety, efficacy, brain penetration, or candidate quality. If a user asks which analog has the \"best chance\" of brain exposure or improved absorption from LogD or pKa alone, report the single-property ranking they requested but explicitly decline the broader conclusion and list the missing evidence.\n"
}

SHA-256: f0c6b7909bd04b2436b0b5854869e9a779ef4f78d3aebdf4a8f8e30a15a907b1