skill Proprietary (Paramus) — guidance only; execution performed by Paramus tools under their own license gating.
Screen a formulation for stability risk by identifying degradation-prone components, predicting stability under stress conditions, and flagging risks with mitigation options — orchestrating Paramus property-prediction and reactivity tools.When to use: a user needs an early read on whether a formulation will stay stable over shelf life or stress.Multi-tool WORKFLOW with stability-risk judgment.

Paramus — Formulation Stability Screen

Overview

Give an early read on formulation stability: flag degradation-prone components, predict behavior under stress, and propose mitigations. The value is the triage across components + conditions, not one lookup.

Guidance vs execution: property, reactivity, and kinetics estimates come from tested Paramus tools. Treat outputs as screening signals, not certified shelf-life claims.

When to Use

  • Early-stage stability risk assessment for a candidate formulation
  • Prioritizing which formulations to put on stability study Do not use for: optimizing ratios to targets (use property optimization) or regulatory shelf-life certification.

Workflow

Formulation composition + storage/stress conditions
  ↓ 1. Identify degradation-prone parts   → hydrolysis/oxidation/pH-sensitive
  ↓ 2. Predict stability under stress      → temperature/humidity/pH effects
  ↓ 3. Screen incompatibilities            → component–component reactivity
  ↓ 4. Flag risks + mitigations            → antioxidants, pH control, packaging
  ↓ 5. Emit risk summary                   → ranked risks + provenance

Procedure

  1. Discover tools via search/get_schema ("stability", "degradation", "reactivity").
  2. Identify components prone to hydrolysis, oxidation, or pH sensitivity.
  3. Predict behavior under the specified stress conditions.
  4. Screen for component–component incompatibilities.
  5. Flag risks with concrete mitigation options.
  6. Emit a ranked risk summary with provenance and confidence.

Domain Judgment

  • Screening ≠ certification — never present predicted stability as guaranteed shelf life.
  • Consider interactions: a stable component can destabilize in the presence of another.
  • Rank by likelihood × impact so the user knows what to test first.

Fallbacks

  • Prediction/reactivity tool unavailable → deliver a manual degradation-pathway checklist, clearly scoped.
  • Endpoint unreachable → stop and report; do not fabricate stability verdicts.