skill Proprietary (Paramus) — guidance only; execution performed by Paramus tools under their own license gating.
Translate an experiment design into an executable robotic protocol and dispatch it to lab automation via Paramus OPERATE, validating the protocol against instrument capabilities and safety constraints before submission and tracking execution.When to use: a user wants to run a planned experiment set on lab robots.Multi-tool WORKFLOW with automation-safety judgment.

Paramus — Robotic Protocol Dispatch

Overview

Convert an experiment design into a validated robotic protocol and dispatch it to lab automation. The value is the design→protocol→validate→dispatch pipeline with safety gating, not one API call.

Guidance vs execution: protocol validation and dispatch run through tested Paramus OPERATE tools. Never bypass validation or send raw instrument commands from ad-hoc code.

When to Use

  • Executing a planned experiment set on liquid handlers / lab robots
  • Translating a design matrix into an instrument-ready protocol Do not use for: designing the experiments (use the campaign planner) or unvalidated hardware control.

Workflow

Experiment design + target instruments + materials/consumables
  ↓ 1. Map design → protocol steps    → operations, volumes, sequence
  ↓ 2. Validate vs instrument caps     → deck layout, volume limits, labware
  ↓ 3. Safety & feasibility checks      → incompatibilities, hazards, collisions
  ↓ 4. Dispatch to OPERATE             → submit protocol, get run handle
  ↓ 5. Track execution & report        → status + provenance + errors

Procedure

  1. Discover tools via search/get_schema ("protocol", "OPERATE", "lab automation dispatch").
  2. Map each design point to concrete operations (transfers, volumes, order).
  3. Validate against instrument capabilities; reject steps that exceed limits.
  4. Run safety/feasibility checks (reactive incompatibilities, hazard flags).
  5. Dispatch only after all checks pass; capture the run handle + provenance.
  6. Track execution status; surface errors immediately, never silently.

Domain Judgment

  • Never dispatch an unvalidated protocol — a failed safety check blocks submission, full stop.
  • Physical actions are irreversible; confirm destructive/hazardous steps explicitly.
  • Keep a full provenance trail (protocol version, instrument, operator/agent) for auditability.

Fallbacks

  • OPERATE/instrument unavailable → produce the validated protocol for manual review; do not simulate a dispatch as if real.
  • Endpoint unreachable → stop and report; never attempt direct hardware control.