SuperAPI AI Directory

opentrons-app

General & other

View repository

Updated 10-16 04:53

About this skill

Opentrons App

Operate the official Opentrons desktop application through the open-computer-use / ocu CLI or its MCP tools.

Core workflow

  1. Verify Open Computer Use is available with ocu -h when its tools are not already exposed by the host.
  2. Ask the user to open the Opentrons App if it is not already running. On Windows and Linux, do not assume Open Computer Use can launch it.
  3. Call list_apps and use the exact matching app or process name.
  4. Call get_app_state before acting. Use text_limit: 1000 or "max" when protocol details, warnings, or run logs are truncated.
  5. Prefer a current element_index and semantic actions. Use window-relative coordinates only when the accessibility tree does not expose the target.
  6. Re-read state after navigation, modal dialogs, robot reconnects, protocol import, or failed actions. Never reuse an index after a major UI change.
  7. Verify the selected robot, robot model, protocol, pipettes, modules, labware, deck locations, and run state against the user's request.
  8. Pause for approval before any consequential action listed below.
  9. Inspect the refreshed state and report what the app shows after every consequential action.

For screen-oriented procedures and recovery guidance, read references/app-workflows.md.

Safety boundary

Perform these read-only actions without additional approval when they are within the user's request:

  • List visible applications and inspect the Opentrons App.
  • Navigate among robot, protocol, device, calibration, and run-detail views.
  • Read connection state, health status, calibration status, run logs, and warnings.
  • Review an imported protocol and its analysis results.

Obtain explicit approval immediately before:

  • Homing or moving robot hardware.
  • Starting, resuming, canceling, or stopping a protocol run, except when stopping immediately is necessary to address a user-reported active hazard.
  • Starting robot, pipette, tip-length, labware, or module calibration.
  • Confirming deck setup when that confirmation advances into hardware movement.
  • Updating robot firmware or the Opentrons App.
  • Deleting protocols, runs, robot data, or calibration data.
  • Uploading or importing a protocol when the user has not already requested that exact file.

Before approving hardware movement, require the user to confirm:

  • The intended robot is selected and physically reachable.
  • The deck matches the displayed labware, modules, adapters, and slot locations.
  • Pipettes and tips match the protocol requirements.
  • The deck is clear of obstructions and the robot door or safety enclosure is in the required state.
  • Liquid identities, volumes, and source/destination wells have been independently reviewed.

Never infer physical deck correctness solely from the GUI. Never dismiss, bypass, or click through a collision, calibration, door, firmware, labware, or protocol-analysis warning without explaining it to the user.

Protocol boundary

Use this skill to operate the App, not to author liquid-handling logic. When protocol generation or validation is required, use the existing opentrons-machine or opentrons-workflow skill first. Return to this skill only after the protocol artifact and physical setup have been reviewed.

Open Computer Use patterns

Use one-off inspection commands when working directly from a shell:

ocu call list_apps
ocu call get_app_state --args '{"app":"Opentrons","text_limit":1000}'

Use a single-process sequence when an action depends on the latest element mapping:

ocu call --calls '[{"tool":"get_app_state","args":{"app":"Opentrons"}},{"tool":"click","args":{"app":"Opentrons","element_index":"REPLACE_WITH_CURRENT_INDEX"}}]'

Do not preserve the placeholder or hard-code an index in reusable instructions. Derive it from the immediately preceding state.

Completion reporting

Report:

  • Selected robot and connection state.
  • Current App screen and run state.
  • Protocol name and analysis status when relevant.
  • Any warning or mismatch observed.
  • Action performed, or the exact action awaiting approval.
  • Refreshed state after an approved action.