AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

opentrons-integration

Authors, reviews, migrates, simulates, and troubleshoots official Opentrons Python Protocol API v2 protocols for Flex and OT-2 robots. Use for robot-specific liquid handling, deck and labware setup, pipettes, modules, runtime parameters, liquid classes, and Opentrons App analysis. Use pylabrobot instead when one workflow must support multiple robot vendors.

Original source
K-Dense-AI
License
MIT
Pinned revision
5f2bc0341354fd5590aef76a533ada1e1e5b4e62

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read k-dense-ai--opentrons-integration at revision 5f2bc0341354fd5590aef76a533ada1e1e5b4e62, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 10

references/sources.md

Upstream Sources

This skill snapshot was verified on 2026-10-01. Opentrons publishes robot software, the desktop/touchscreen Apps, the Python package, and Protocol API levels on related but distinct release cycles. Recheck time-sensitive facts before generating a production protocol.

Verified Baseline

  • Stable PyPI package: opentrons==10.0.0, released 2026-09-30, requiring Python 3.10 or newer. Local tests used Python 3.12 because the package requires NumPy below 2. This package targets Flex.
  • Local OT-2 API 2.28 compatibility simulation uses opentrons==9.0.0, the tested shared-line PyPI release that accepts OT-2 protocols at that API level.
  • Current robot-software support documented by Opentrons:
    • Flex: API 2.15–2.30; API 2.30 maps to robot software 10.0.0.
    • OT-2: API 2.0–2.28.
  • API 2.29 and newer use separate Flex and OT-2 software/App release lines.

opentrons==10.0.0 rejects OT-2 simulation and directs users to the separate OT-2 App. The target robot's maximum API value and analysis result in the appropriate App are authoritative for whether a specific protocol can run.

The released 10.0.0 Python library reports MAX_SUPPORTED_VERSION=2.31, while the official robot support table stops at 2.30. This skill uses the documented robot ceiling and retains API 2.29 for its bundled Flex templates. API 2.30's start-only meniscus fix is separately simulation-tested. Do not treat a local constant or successful simulation as evidence of support on a physical robot.

All six bundled templates were simulated: five with 10.0.0, and OT-2 with 9.0.0. Tests also exercise runtime-parameter boundaries, low-volume modes, meniscus behavior, Heater-Shaker tasks, and tip reuse semantics. Reference code fragments require the surrounding deck and liquid setup; unless covered by these tests, they are illustrative and were checked against official docs and released method signatures rather than executed as complete protocols. No robot, App, sensor, or physical assay validation was performed.

Core Protocol API Documentation

Pipettes and Liquid Handling

Parameters, Labware, and Deck

Hardware Modules

Robot and App User Guides

Releases and Source

Separate HTTP API Surface

The Python Protocol API is the preferred surface for protocol files. Direct robot-server integrations are separate:

  • HTTP API specification — published OpenAPI description.
  • A target robot also serves its OpenAPI document on port 31950.

Use the specification served by the target robot when integrating directly. Do not translate Protocol API methods into guessed HTTP endpoints.

Source Precedence

When sources differ:

  1. Target robot's maximum API and analysis result in the appropriate App.
  2. Current official versioning and API reference.
  3. Current robot/module instruction manual.
  4. Stable PyPI metadata and tagged GitHub release.
  5. Example protocols.

Examples can lag the versioning page or show a higher generic API level than a particular robot currently supports. Apply the target robot's maximum.