opentrons-integration

The Opentrons Integration skill provides a comprehensive environment for researchers and lab automation engineers to develop Python-based protocols for Opentrons OT-2 and Flex robotic platforms. This skill centers on the Protocol API v2, allowing users to automate precise liquid handling workflows such as serial dilutions, PCR plate preparation, and complex reagent transfers. It is designed for laboratory environments requiring high-throughput screening, sample preparation, or automated assays. Users can manage hardware configurations, including pipette mounts, labware layouts, and specialized modules such as the Temperature Module, Magnetic Module, Heater-Shaker, and Thermocycler, ensuring full reproducibility in experimental protocols.

• Full support for Opentrons Protocol API v2 syntax and metadata structure.

• Capabilities for defining deck layouts, including slot management for plates, reservoirs, and custom labware.

• Fine-grained control over liquid handling parameters: aspiration/dispensing volumes, flow rates, air gaps, blowout, and touch-tip functions.

• Support for multi-channel pipettes and 96-well plate operations to maximize experimental throughput.

• Integration with core hardware modules: heater-shaker, thermocycler, and magnetic modules for advanced chemical and biological workflows.

• Standardized protocol metadata (author, description, apiLevel) to ensure compatibility with robot fleet management.

• Always define the API version in the metadata to ensure compatibility with the target robot's firmware version.

• Protocol logic must be encapsulated within the run(protocol: protocol_api.ProtocolContext) function to be valid for execution.

• Utilize specific naming conventions for instruments (e.g., p1000_single_flex) and labware (e.g., corning_96_wellplate_360ul_flat) as defined by the Opentrons API.

• The skill is intended strictly for Opentrons ecosystem hardware; for multi-vendor lab automation needs, consider alternative frameworks like PyLabRobot.

• Ensure all tip management and labware loading steps are explicitly defined to prevent hardware collisions during simulation and physical execution.